You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using this module and having it create a access log bucket, if you use a module.app_label.id that is too long (in this case it was 48 characters) then it will truncate the access log bucket name. But the usage of this truncated name is inconstant. The issue that we have run into is with the bucket policy. In the ForceSSLOnlyAccess statement it is using the truncated/correct bucket name. In the other three statements it is using a non-truncated version of the bucket name that doesn't exist.
Expected Behavior
The correct bucket name gets used everywhere
Steps to Reproduce
Use this module with app label ID with a length of 48 characters or above an let it create an access log bucket for you.
Describe the Bug
When using this module and having it create a access log bucket, if you use a
module.app_label.id
that is too long (in this case it was 48 characters) then it will truncate the access log bucket name. But the usage of this truncated name is inconstant. The issue that we have run into is with the bucket policy. In theForceSSLOnlyAccess
statement it is using the truncated/correct bucket name. In the other three statements it is using a non-truncated version of the bucket name that doesn't exist.Expected Behavior
The correct bucket name gets used everywhere
Steps to Reproduce
Use this module with app label ID with a length of 48 characters or above an let it create an access log bucket for you.
Screenshots
Trying to add the above policy results in the following error
Environment
module version: 1.11.1
Additional Context
No response
The text was updated successfully, but these errors were encountered: