-
Notifications
You must be signed in to change notification settings - Fork 69
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
Migrate to CFT logging modules #613
Conversation
expiration_days = 7*365 | ||
retention_policy = { | ||
is_locked = true | ||
retention_period_days = 6 * 365 |
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.
what's the different between the retention_period_days
here and expiration_days
above? and why are they set to different values?
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.
Retention period does not actually do anything. It just forces the bucket to permanently have an expiry that is at least this amount. See https://cloud.google.com/storage/docs/bucket-lock. I also added a comment.
p.s. there seems to be an org policy we should probably set as well: https://cloud.google.com/storage/docs/org-policy-constraints#audit-logging. Do you want to look into that?
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.
sure i'll look into that.
I have upstreamed features from DPT into the CFT logging modules so they mostly match our feature set. They also have new features to set things like bucket locks which are useful for hipaa alignment.