-
Notifications
You must be signed in to change notification settings - Fork 155
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
Feature Request: AddClientIDToOpenIDConnectProvider #4460
Comments
@yambottle you should be able to add a new client to an OpenIDConnectProvider using the OpenIdConnectProvider resource. If you are not currently managing the |
Hi @corymhall ,
I have two Pulumi projects, the first one provisions organizational infra and each organization has a different AWS account; the second one provisions infra for each team within its organizational AWS account, and in my case, each team has a different client_id, but they need to have the same OIDC provider. With only OpenIdConnectProvider resource, I can only think of a solution that My solution
Is there anything incorrect with how I deal with this? If not, I was thinking adding a function |
@yambottle thanks for the additional details. In these types of cases what I've done in the past is continue to centrally manage the If that doesn't work for your use case and you do need to be able to modify the |
@corymhall Thanks! Just created a request. For a temporary walk-around, I'll use boto3 add_client_id_to_open_id_connect_provider in the downstream script for now. |
Hi there,
I'm looking for a feature to add or attach new Client ID/Audience to an existing OIDC provider API doc
The text was updated successfully, but these errors were encountered: