-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: wasmbus Policy / Config / Secrets Services #157
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Lucas Fontes <[email protected]>
af7aa29
to
9ee1883
Compare
Signed-off-by: Lucas Fontes <[email protected]>
Signed-off-by: Lucas Fontes <[email protected]>
hold on I will bring the secrets service over too real quick |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks nice 👍🏻
// NOTE(lxf): this covers components but not providers. wut?!? | ||
Target InvocationTarget `json:"target"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By covers, do you mean that this isn't present when providers call components? Or that you can't actually use this to call a provider
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I couldnt find any mention to providers related to Policy, and the InvocationTarget
struct doesn't include any provider info.
it's unclear if this is by design or if we missed providers here.
Signed-off-by: Lucas Fontes <[email protected]>
Signed-off-by: Lucas Fontes <[email protected]>
secrets are in! good to review 🙇 |
Implementing Policy & Config services: