fix(OpenIDConnectProvider): inaccessible providers #576
+19
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Deofex
force-pushed
the
inaccessible-open-id-connect-providers
branch
from
d004d34 to
6469331
Compare
Deofex
force-pushed
the
inaccessible-open-id-connect-providers
branch
from
6469331 to
851facc
Compare
ekristen
approved these changes
Feb 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When running
aws-nukewith a user that lacks permissions to retrieve details about a specificOpenIDConnectProvider, the tool currently skips allOpenIDConnectProviderresources. This fix ensures thataws-nukelogs the error but continues processing, aligning its behavior with how other resources are handled.