gray-elephant-3769504/17/2019, 2:45 PM
- so that these can be passed once to a component and automatically inherited by all children of that component.
It looks like https://pulumi.io/reference/programming-model.html#components isn't yet clear on these three points - so I'll make sure we update that.
gray-elephant-3769504/17/2019, 6:54 PM
My thinking is the key benefit pulumi provides is that we can finally build our infra with code so it should allow for maximum flexibility with respect to which paradigms can be used with it.Totally agreed, and we've seen quite a few patterns for constructing components. In general, I haven't seen any specific API design patterns that can't be built on top of the ComponentResource abstraction (perhaps just as an implementation detail internal to the API) - but would love to see details on the kind of API design that doesn't currently fit into this model and what we could do to enable it.