-
Notifications
You must be signed in to change notification settings - Fork 217
Expose dependent configuration for the case where we have several dependents of the same type #857
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
Comments
Thinking about this, I see two kinds of multiple dependents of same type:
|
Yes, I tend to think that we should limit ourselves to the fixed case as a start and see how it goes and if we need to make it more dynamic. |
@csviri can you please point out the documentation or example code to see how this is working? Thanks a lot in advance! |
@andreaTP pls take a look here: Note that this is on |
Thanks for the pointer @csviri , does it make sense to provide "default" discriminators based on something pretty standard like |
usually I think that would be based on rather some naming convention of the resource. So not sure. Might be if we seem some patterns. |
@csviri is this feature available now? If yes, could you please share some example code? (sorry, but example you've shared above is not very clear) |
@bachmanity1 no, it will come with 4.1 (see milestone). It will be documented for that release too. |
ok, got it. Thanks for quick reply. |
How do dependents work when we have more than one secondary resource (like having 3 deployments) ?
Originally posted by @sebastienblanc in #785 (comment)
The text was updated successfully, but these errors were encountered: