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.

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

Spanner Database Resource should support versionRetentionPeriod and earliestVersionTime #544

Closed
knechtionscoding opened this issue Sep 13, 2021 · 7 comments
Labels
enhancement New feature or request

Comments

@knechtionscoding
Copy link

Describe the feature or resource
Spanner Database Resource should support setting the versionRetentionPeriod and earliestVersionTime to allow for PITR:

https://cloud.google.com/blog/products/databases/continuous-data-protection-here-for-spanner-with-pitr

type SpannerDatabaseSpec struct {
/* An optional list of DDL statements to run inside the newly created
database. Statements can create tables, indexes, etc. These statements
execute atomically with the creation of the database: if there is an
error in any statement, the database is not created. */
// +optional
Ddl []string `json:"ddl,omitempty"`
/* Immutable. Encryption configuration for the database */
// +optional
EncryptionConfig *DatabaseEncryptionConfig `json:"encryptionConfig,omitempty"`
/* The instance to create the database on. */
InstanceRef v1alpha1.ResourceRef `json:"instanceRef"`
/* Immutable. Optional. The name of the resource. Used for creation and acquisition. When unset, the value of `metadata.name` is used as the default. */
// +optional
ResourceID *string `json:"resourceID,omitempty"`
}

Importance

Currently this has to be set manually via the console or the cli rather than being stored in the cnrm config for the resource. Would greatly improve the ability to provision spanner via cnrm

@knechtionscoding knechtionscoding added the enhancement New feature or request label Sep 13, 2021
@knechtionscoding
Copy link
Author

Based on the other Issues/PRs I see we need to wait for terraform to support it: hashicorp/terraform-provider-google#8994 will solve this.

@toumorokoshi
Copy link
Contributor

Hi!

Based on the other Issues/PRs I see we need to wait for terraform to support it: hashicorp/terraform-provider-google#8994 will solve this.

Yes, exactly. Once it's in Terraform expect a 2-3 week maximum delay for it to appear in the next version of Config Connector.

@knechtionscoding
Copy link
Author

@toumorokoshi based on: GoogleCloudPlatform/magic-modules#6141 and the other issue being closed for 30 days, should we expect this to land in config connector in the next release? Or is it already available?

@toumorokoshi
Copy link
Contributor

Hi! Just as an FYI I've moved teams, so may not able to help as much.

I took a quick look at the docs and I don't see the field appearing yet. Likely it will be picked up a Terraform update in the next week or so.

An engineer working on the product should be able to reply soon with more details.

@mbzomowski
Copy link

@knechtionscoding Likely we will update Config Connector's Terraform provider next week, so this change should be included in our release the week after that, which will be Config Connector v1.92.0.

@mbzomowski
Copy link

@knechtionscoding correction - we won't be updating our Terraform provider this week. We should be updating it two weeks from now, so this change will be included in our release 3 weeks from now.

@cheftako
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants