Add acceptance and internal tests for gcs
backend, add some test helper functions
#35026
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.
Historically the
gcs
backend hasn't been touched much. In the past I've added a few features but largely left the existing codebase as it was previously. Recently thegcs
backend was refactored in #34989 to avoid using the old SDK.As part of reviewing that PR I started adding a few acceptance tests in this PR. There's a lot more work to be done but I want to avoid this PR getting too big.
This PR:
gcs
backend set up (//TODO!)TestBackendConfig_encryptionKey
- how the config and ENVs for customer-supplied encryption keys are usedTestBackendConfig_kmsKey
- how the config and ENVs for customer-managed (KMS) encryption keys are usedTestAccBackendConfig_credentials
- empty strings in the backend config don't interrupt use of ENVs for creds.Target Release
1.8.x
Draft CHANGELOG entry
NEW FEATURES | UPGRADE NOTES | ENHANCEMENTS | BUG FIXES | EXPERIMENTS