feat: S3 secret environment variable #16
Open
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.
Tweak to how S3 secret is read. First the AppSetting for S3SecretKey is read, if that is null then it searches for S3SecretEnvironmentVariable for a tenant level env var.
This will initially not be present in agreements/licenses, and so null/empty-safeing has been introduced to AppSetting.getSettingValue.
Finally if all above have returned null, fall back to GLOBAL_S3_SECRET_KEY
refs ERM-3470