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.

Sign up for GitHub

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

Jump to bottom

Upgrade crossguard content to aws.s3.BucketV2 #13013

Open
t0yv0 opened this issue Oct 2, 2024 · 0 comments
Open

Upgrade crossguard content to aws.s3.BucketV2 #13013

t0yv0 opened this issue Oct 2, 2024 · 0 comments
Assignees
@t0yv0
Labels
area/docs Improvements or additions to documentation

Comments

@t0yv0
Copy link
Member

t0yv0 commented Oct 2, 2024

Policy packs written against aws.s3.Bucket do not translate to aws.s3.BucketV2 setups in a straightforward way, especially when deprecated attributes like "acl" are taken into account. The affected content lives here:

content/docs/iac/packages-and-automation/crossguard

Separating this out into a dedicated ticket as there is a bit of work involved here.

References
@pulumi-bot pulumi-bot added the needs-triage Needs attention from the triage team label Oct 2, 2024
@github-project-automation github-project-automation bot moved this to 🤔 Triage in Docs 📚 Oct 2, 2024
@t0yv0 t0yv0 mentioned this issue Oct 2, 2024
Merged
@interurban interurban added area/docs Improvements or additions to documentation and removed needs-triage Needs attention from the triage team labels Oct 8, 2024
@thoward thoward moved this from 🤔 Triage to 🧳 Backlog in Docs 📚 Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@t0yv0 t0yv0

Labels
area/docs Improvements or additions to documentation
Projects
Docs 📚
Status: 🧳 Backlog
Milestone
No milestone
Development

No branches or pull requests
3 participants
@t0yv0 @interurban @pulumi-bot