Closed slavizh closed 1 year ago
It is not possible for the user to specify a different deny setting for each resource. However, there are some scenarios where different resources in the same stack may have a different status (deny assignment failed to update, or a resource was created outside the scope of the deployment). Therefore, we have denyStatus per-resource, even though the denySettings are per-stack.
Does that help clarify the usage?
Yes, this clarifies it. Thanks!
Is your feature request related to a problem? Please describe. When you look at the managed resources you have the ID and DenyStatus for each resource. Is it possible to set different denyStatus per resource? I cannot remember if that was one of the goals for private preview 2.
Describe the solution you'd like A clear and concise description of what you want to happen.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.