-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
support for point in time restore aws api for aws rds #65
Comments
It looks like the aws provider is lacking this functionality. This issue will need to be implemented first before this module will be able to implement this feature as requested above if I understand things correctly: hashicorp/terraform-provider-aws#5286 |
as @pjroth pointed out, this should be opened on the upstream provider |
It looks like the issue I linked above in aws provider has now implemented this feature. It looks like there is nothing technical preventing this issue from being worked on at this time. Should this be kept open @bryantbiggs? |
hey @pjroth - yes point in time restore support is available in the provider and an issue can definitely be created to add this support into the module. however, this issue is more geared towards the upstream provider and references the golang implementation details, etc. and therefore is not sufficient here for this module |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Hi:
I am using the terraform-aws-rds module for one of our terraform project at work and recently have been looking into support for restore of aws rds (postgres specifically) using snapshot and PITR (point in time restore) api's that aws provides. terraform-aws-rds module today already support snapshot based restore but not PITR agreeably because terraform-provider-aws also does have have PITR support today.
I have opened this issue on git hub for the same for terraform-provider-aws: hashicorp/terraform-provider-aws#5286
Can someone share details on how I can contribute to the terraform-aws-rds module or if someone can provide support below PITR feature. Did not see any instructions to contribute on the terraform-modules github page. May be I can copy the module locally and make changes there?
Here are more details:
Beyond adding relevant code in terraform-provider-aws in this go file for PITR, I realized that I need to also update the terraform-aws-rds module that I am consuming to recognize the new variables that I need to support for PIRT.
This is a draft version of changes I am playing with in the resource_aws_db_instance.go on my local machine. As you can see I basically added four new arguments
SourceDBInstanceIdentifier: aws.String(d.Get("source_db_instance_identifier").(string)), TargetDBInstanceIdentifier: aws.String(d.Get("target_db_instance_dentifier").(string)), UseLatestRestorableTime: aws.Bool(d.Get("use_latest_restorable_time").(bool)), RestoreTime: aws.Time(d.Get("restore_time").(time.Time)),
And got rid of below that's required for snapshot based restore.
// DBInstanceIdentifier: aws.String(d.Get("identifier").(string)), // DBSnapshotIdentifier: aws.String(d.Get("snapshot_identifier").(string)),
Potential change to support PITR:
else if _, ok := d.GetOk("source_db_instance_identifier"); ok {
My terragrunt plan is now failing as the terraform-aws-rds modules does not recognize the new parameters I introduced to support PITR and also complaining about the identifier that's not required for PIRT unless I replace target_db_instance_identifier as identifier.
`
terragrunt plan --terragrunt-source ../../../../../../../terraform-modules//rds/postgresql/restore/PITR
...
...
...
Initializing the backend...
Error: module "db": "source_db_instance_identifier" is not a valid argument
Error: module "db": "target_db_instance_identifier" is not a valid argument
Error: module "db": "use_latest_restorable_time" is not a valid argument
Error: module "db": missing required argument "identifier"
`
Looking forward to get the PITR support in terraform-aws-rds module (and also terraform-provider-aws ultimately which is a dependency for sure for the rds module to work).
The text was updated successfully, but these errors were encountered: