Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Notifications submodule buckets ARN generation in alternate partitions (e.g. GovCloud) #159

Closed
tculp opened this issue May 16, 2022 · 2 comments · Fixed by #165
Closed

Comments

@tculp
Copy link

tculp commented May 16, 2022

Is your request related to a problem? Please describe.

The notifications submodule generates the bucket ARN with

locals {
  bucket_arn = coalesce(var.bucket_arn, "arn:aws:s3:::${var.bucket}")
...

However, this does not work when the partition of the ARN is not aws, e.g. in GovCloud.

Describe the solution you'd like.

The module should use the aws_partition data source to pull the current provider's partition.

Describe alternatives you've considered.

Specifying the bucket ARN directly.

This is strange because you then need to specify both the bucket and bucket_arn variables, since neither is computed from the other, and both are used in different resources.

@tculp tculp changed the title Notifications submodule doesn't work with buckets in alternate partitions (e.g. GovCloud) Notifications submodule buckets ARN generation in alternate partitions (e.g. GovCloud) May 16, 2022
@tculp tculp changed the title Notifications submodule buckets ARN generation in alternate partitions (e.g. GovCloud) feat: Notifications submodule buckets ARN generation in alternate partitions (e.g. GovCloud) May 16, 2022
@tculp
Copy link
Author

tculp commented May 16, 2022

I noticed after creating this feature request that the bucket_arn variable also exists, so I updated the request accordingly.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant