Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Registration of inbox at initialization or in the policy? #9

Open
mielvds opened this issue Jun 1, 2021 · 2 comments
Open

Registration of inbox at initialization or in the policy? #9

mielvds opened this issue Jun 1, 2021 · 2 comments
Assignees

Comments

@mielvds
Copy link
Contributor

mielvds commented Jun 1, 2021

Is the registration of inbox and resources to watch something we want to do at initialization or do we write this in the policy so that they are automatically registered when the policy is?

@mielvds mielvds changed the title is this registration of inbox, resources something we want to do at initialization or do we write this in the policy? Registration of inbox at initialization or in the policy? Jun 1, 2021
@mielvds
Copy link
Contributor Author

mielvds commented Jun 15, 2021

As discussed:

  • defining how an ochestrator gets to its inboxes is not necessary
  • in the registration phase, not really initialization (orchestrator can still receive other triggers)

@phochste phochste self-assigned this Oct 11, 2021
@phochste phochste added this to the milestone1 milestone Oct 12, 2021
@phochste
Copy link
Contributor

This is more something for a milestone 2 or later how the registration of an orchestrator can be done

@phochste phochste removed this from the milestone1 milestone Oct 14, 2021
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants