You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support of managing multiple similar resources dynamically - depending on the specs of the primary resource.
To be able to discriminate which dependent resource we are managing the desired should receive the index of the resource:
protected R desired(P primary, Context<P> context, int index) or inside the Context object. (This would require an extended Context for the dependent resources.
Questions to clarify/discuss
Should be this on top level. Thus directly the DependentResource interface should support this?. And have a wrapper dependent resource over that, that supports count? (basically agree on class level design)
Support of managing multiple similar resources dynamically - depending on the specs of the primary resource.
To be able to discriminate which dependent resource we are managing the desired should receive the index of the resource:
protected R desired(P primary, Context<P> context, int index)
or inside theContext
object. (This would require an extendedContext
for the dependent resources.Questions to clarify/discuss
Should be this on top level. Thus directly the
DependentResource
interface should support this?. And have a wrapper dependent resource over that, that supports count? (basically agree on class level design)Notes
count
in terraform, see: https://www.terraform.io/language/meta-arguments/countDependentResource
support for event sources where multiple resources of same type are handled for single primary #1175The text was updated successfully, but these errors were encountered: