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

Support minutes and seconds values for maxAge attribute of the Bigtable Garbage Collection Policy (GCP) #345

Closed
wesam80 opened this issue Dec 14, 2020 · 3 comments
Closed

Support minutes and seconds values for maxAge attribute of the Bigtable Garbage Collection Policy (GCP) #345

wesam80 opened this issue Dec 14, 2020 · 3 comments
Labels
enhancement New feature or request

Comments

@wesam80
Copy link

wesam80 commented Dec 14, 2020

It seems that the smallest maxAge value we can get using config-connector is days

We are looking for minutes.

Google's documentations states that the supported time units are days, minutes, and seconds
@wesam80 wesam80 added the enhancement New feature or request label Dec 14, 2020
@caieo caieo mentioned this issue Dec 15, 2020
Closed
@caieo
Copy link
Contributor

caieo commented Dec 15, 2020

Hi @wesam80, I filed an issue against the Google Terraform provider to support minute and seconds for the maxAge field. Once that's done, we will bring that change over to ConfigConnector's BigtableGCpolicy resource. We will post any updates in this issue thread.

@kevinsi4508
Copy link

This should be resolved by using gc_rules. Currently we are waiting for KCC to update to the latest Google Terraform Provider version.

@mbzomowski
Copy link

spec.gcRules has been added to BigTableGCPolicy as of Config Connector v1.97.0. We don't recommend using maxAge, maxVersion or mode for defining a
BigTableGCPolicy as these fields have known drift detection issues. Please use gcRules instead.

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

No branches or pull requests
3 participants
@kevinsi4508 @mbzomowski @caieo