Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork878
feat: support for date partitioned logging keys#282
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Looks good@NathanBaulch, thanks for this.
Could you please also runmake readme to update the docs?
Uh oh!
There was an error while loading.Please reload this page.
Looks like |
Ah ok - that's news to me also. I'll look into it. |
So it was just (on a mac): brew install atmosatmos readme https://atmos.tools/install for other platforms. I've rebuilt the readme. Please check the linting error:https://github.com/cloudposse/terraform-aws-s3-bucket/actions/runs/18861770411/job/53821423651?pr=282 |
Might be worth documenting the accepted values for |
what
A couple of years ago AWS introduced the option to format S3 access log keys by forward slash instead of hyphen "to speed up analytics and query applications" (quote from AWS Console).
This requires bumping the AWS provider to v5.27. I'm not sure about the wider implications of that.
why
I'd like to access this feature in my IaC scripts.
references
https://registry.terraform.io/providers/hashicorp/aws/5.27.0/docs/resources/s3_bucket_logging#target_object_key_format