pulumi
Not all input properties are available as output properties
I haven’t investigated to see how widespread it is across the codebase, but the example occurrence I came across is in containerservice’s ManagedCluster. The documentation states that “all input properties are implicitly available as output properties”, but resourceGroupName, an input property, is not present as an output property. This can also be verified by inspecting the file.
So, is that omission a bug? Or is that claim in the documentation obsolete?
Good point. Currently, the inputs that are part of the resource path aren't exposed as outputs (because they aren't in the HTTP response from Azure). We'll take a look at reconciling the behavior vs. the docs.
Same question here, old Azure provider does provide inputs as outputs, which helps a lot to decouple infra logic. Currently, you need to repeat resourceGroupName N-times for each subsequent resource creation.
Hit the same issue with Service Bus namespace. Would be great if the resource group name was exposed as an output.
This is also bothering us a lot, with Azure SQL databases, serverName and resourceGroupName are not available as outputs.
Is this blocked? It has already been more than 3 years :)
Note that this is distinctly bad in Python, where properties like resource_group_name are still generated but return null at runtime, see https://github.com/pulumi/pulumi-azure-native/issues/3082
@justinvp @Frassle this isnt a must have but is something that is blocking implementation of certain azure stack policies.
@tyler-dunkel, this is up to the Azure Native provider team (cc: @pulumi/providers) to decide that inputs should be propagated to outputs for Azure Native resources. But fundamentally, the shape of inputs and outputs can be different, which is why I'm concerned if we're passing resource outputs to Analyze (for resource policies), which is intended to receive resource inputs.
CC @pgavlin who may be able to explain in more detail but we are using outputs on the insights side to eval resource policies.
However, this is for stack policies.