Fix AWS SecretsManager providers to handle empty fieldName when secret is non-JSON #189
Conversation
This file contains hidden or 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
oracle-contributor-agreement
bot
added
the
OCA Verified
jeandelavarene
approved these changes
Jun 10, 2025
jeandelavarene
deleted the
fix/aws-secretsmanager-error-on-empty-fieldname-with-non-json
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #188
When a secret stored in AWS Secrets Manager contains plain text and the
fieldNameparameter is set to an empty string, an IllegalStateException was previously thrown.This PR solves the problem by ensuring that the
fieldNameparameter is only used when it's explicitly provided and not empty.Also added test cases for all resource providers to verify this behavior.