Pat Gavlin

> @pgavlin out of curiosity, is the default/internal permission set to `open`, then, for Team Edition? No--it is set to `write`.

> @pgavlin are there docs explaining the difference between those different options? > > Maybe I don’t understand the ins and outs but the fear is a a default read...

(edited the above to clarify that users with `read` permission for an environment cannot view secrets at all)

> @pgavlin thanks for the insight! Are wildcards supported when we grant open access to specific environments? They are not, unfortunately. The default environment permission is the closest thing we...

I’m wondering if there’s a way to make this work without needing to touch all of our providers. The larger picture here is that it’s not pulumi per se that...

@lukehoban #3304 is this issue... did you mean to link to something else?

Cross-posting from pulumi/esc#199: https://github.com/pulumi/esc/issues/199#issuecomment-2164123853

This is semi-intentional. The reason that `` is in there is that we play a bit of a trick with stack environments. In order to maintain the same sort of...

Similar to https://github.com/pulumi/pulumi/issues/3529, I'm guessing that the `ignoreChanges` property on the `awsx.ecs.FargateService` component resource is not being propagated to its children. Until that is fixed, I believe that you can...

> Should I create a ComponentResource to encapsulate them? Yes, I think that's a reasonable path forwards. It's been a while since I had my nose in this code, so...