issue#515: Move check for config secrets from the read to the update in conn #517
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.
🔧 Changes
We are moving the check for unmanaged configuration secrets on Database Connections over from the read to the update func. The check should have only alerted the user when they're trying to update and not when reading as well, as the same func is also reused within the conn data source.
📚 References
🔬 Testing
This PR adds a new test as well that uses the import functionality of a pre-configured db conn with an unmanaged config secret. The test can only run with the test recordings due to the initial work needed to set it up.
📝 Checklist