nasa-veda: add bucket permissions to terraform added outside terraform #3722
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.
@freitagb I detected a change in nasa-veda's cloud infra that wasn't reflected in our terraform configuration.
When re-generating credentials (#3723), I had to either delete what was added outside the terraform config in the terraform managed resource (bucket permissions), or I had to add it. I opted to add it to the terraform configuration, and while doing that I also added the same permission for the staging environment.
The change applied outside our terraform configuration was to make an IAM Policy allowing bucket access apply to the bucket
sdap-dev-zarr
.@freitagb could you confirm its OK to persist this change to the terraform config for use in both staging/prod?