Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws-ts-oidc-provider-pulumi-cloud fails if there's no OIDC provider present #1713

Open
jkodroff opened this issue Oct 11, 2024 · 0 comments
Open
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team

Comments

@jkodroff
Copy link
Member

What happened?

If there's no OIDC provider, aws.iam.getOpenIdConnectProviderOutput throws an exception. We probably need to put this into a try/catch or use the Command provider to check for the existence of an existing provider as there's no function to check for OIDC providers that returns a list.

Example

n/a - see above

Output of pulumi about

n/a - This isn't related to any particular provider version.

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).

@jkodroff jkodroff added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Oct 11, 2024
@jkodroff jkodroff self-assigned this Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team
Projects
None yet
Development

No branches or pull requests

1 participant