-
Notifications
You must be signed in to change notification settings - Fork 13
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
added BackupRetentionPeriod config #173
Conversation
8493944
to
c1e1c8d
Compare
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.
should we account aurora workflow?
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 are we specifying in the backupRetentionPeriod
field?
c1e1c8d
to
9e73360
Compare
@bjeevan-ib I've added this config for DBCluster as well. Usually, backup retention period can't be set to 0 for aurora but the value can be managed with DBCluster.
@abalaven this field is used to set the number of days for which automated backups are retained. More about this is here: https://doc.crds.dev/github.com/crossplane/provider-aws/rds.aws.crossplane.io/DBInstance/[email protected]#spec-forProvider-backupRetentionPeriod |
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.
IIUC, the default value for backupRetentionPeriod
is set to 0 in the values file, which I believe will be added to the configMap. Is there any provision to set the value independent of the CM? The CM only holds default values if I'm not wrong.
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.
Use a string and pass it through time.ParseDuration()
. time.Duration is represented as int64 in nanoseconds, so this will be ridiculous to configure if somebody wants 365 days
backup: 3.1536e16
Metav1.Duration is the standard kubernetes serialization of a golang
duration. It should allow controller to unmarshal to the time.Duration
https://github.com/kubernetes/apimachinery/blob/master/pkg/apis/meta/v1/duration.go
…On Mon, Sep 11, 2023, 14:02 Drew Wells ***@***.***> wrote:
***@***.**** requested changes on this pull request.
Use a string and pass it through time.ParseDuration(). time.Duration is
represented as int64 in nanoseconds, so this will be ridiculous to
configure if somebody wants 365 days
backup: 3.1536e16
—
Reply to this email directly, view it on GitHub
<#173 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB7SRDOK7OPOBGU7JXHRI23XZ5N3FANCNFSM6AAAAAA4OL7QEI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@drewwells @pjferrell, as per docs it only accepts value from 0-35 (0 means disabled) and it denotes number of days. We can't set it beyond 35. |
9e73360
to
2332a20
Compare
@abalaven I initially tried using arguments to db-controller to pass such values but it required multiple function signature changes. Also we don't want it to be set at dbclaim level but db-controller so CM seemed a good option as it's already configured to take db-controller config as input. Added something similar here: #172 |
2332a20
to
83664a2
Compare
V1 Story: B-98504
Added BackupRetentionPolicy flag to configure it for prod and non-prod envs