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
But it is not clear to me if doing this deletes the oidc provider for ESC as well. I see it says "all of the resources are destroyed" but does the oidc provider live on after the stack is destroyed? I am asking here because the doc does not make it clear if the stack is essential to create the oidc resource or if the stack needs to remain to keep the oidc provider active in aws.
Example
It could be that the deletion comment is just part of the lifecycle of the oidc provider that when you are done with using it you can delete it but if you intend on using it the intention should not be delete it right afterwards. There should be some additional wording "now that the oidc provider is ready you are ready to continue using ESC."
The wording does not explain if it lives on in AWS after the stack is deleted or not. This ambiguity is difficult for users to understand what is meant without manually testing it.
Also shouldn't the stack name used in the example be more purposeful then the name 'dev' when it could instead be 'oidc' to make it clear that is what the stack is for?
Output of pulumi about
NA
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered:
What happened?
At the end of this document here https://github.com/pulumi/examples/tree/master/aws-py-oidc-provider-pulumi-cloud it suggests you can delete the stack used to create the pulumi cloud oidc resource "Once you are done, you can destroy all of the resources as well as the stack:"
But it is not clear to me if doing this deletes the oidc provider for ESC as well. I see it says "all of the resources are destroyed" but does the oidc provider live on after the stack is destroyed? I am asking here because the doc does not make it clear if the stack is essential to create the oidc resource or if the stack needs to remain to keep the oidc provider active in aws.
Example
It could be that the deletion comment is just part of the lifecycle of the oidc provider that when you are done with using it you can delete it but if you intend on using it the intention should not be delete it right afterwards. There should be some additional wording "now that the oidc provider is ready you are ready to continue using ESC."
The wording does not explain if it lives on in AWS after the stack is deleted or not. This ambiguity is difficult for users to understand what is meant without manually testing it.
Also shouldn't the stack name used in the example be more purposeful then the name 'dev' when it could instead be 'oidc' to make it clear that is what the stack is for?
Output of
pulumi about
NA
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: