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

Add influxdb_bucket_retention_rules parameter #141

Conversation

SimonHoenscheid
Copy link
Contributor

Add influxdb_bucket_retention_rules parameter to make retention rules configurable

Since puppetlabs/influxdb#71 is merged and released with version v1.6.0 of the influxDB module, updating the module without modifying the retention rules results in data loss on the users end. This patch just adds the option to do this.

@SimonHoenscheid SimonHoenscheid requested a review from a team as a code owner February 28, 2023 14:22
@puppet-community-rangefinder
Copy link

puppet_operational_dashboards is a class

Breaking changes to this file MAY impact these 1 modules (near match):

This module is declared in 0 of 580 indexed public Puppetfiles.


These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

@SimonHoenscheid
Copy link
Contributor Author

@m0dular @MartyEwings may I ask for a release after this is merged?

@MartyEwings MartyEwings added the enhancement New feature or request label Feb 28, 2023
@MartyEwings
Copy link
Collaborator

@m0dular is a 90 day default with the justification that an upgrade is not impacting, cool with you?
We would need to put some config on our platforms on next upgrade to compensate

@SimonHoenscheid
Copy link
Contributor Author

@MartyEwings

@m0dular is a 90 day default with the justification that an upgrade is not impacting, cool with you? We would need to put some config on our platforms on next upgrade to compensate

I created the PR because the mentioned change in the Influxdb module is a breaking one. This change just gives the user the option to change the default (coming from the influx module)

Influx Bucket before Influxdb 1.6.0 release:

influx bucket list
ID                      Name            Retention       Shard group duration    Organization ID         Schema Type
d3e7bebd27375b07        puppet_data     infinite        168h0m0s                c8d85d6a80ef4af3        implicit

after:

influx bucket list
ID                      Name            Retention       Shard group duration    Organization ID         Schema Type
d3e7bebd27375b07        puppet_data     2160h0m0s       168h0m0s                c8d85d6a80ef4af3        implicit

@m0dular
Copy link
Contributor

m0dular commented Feb 28, 2023

I'm a little worried this would create a duplicate declaration if people are managing the initial bucket themselves. You can always manage it in Puppet code with the retention and any other params you need, but I think if there were also a $manage_initial_bucket parameter in this PR then it would be good. The other side of the coin is that infinite retention would keep using disk space, so I think we did need a default.

@m0dular
Copy link
Contributor

m0dular commented Feb 28, 2023

Nevermind, I thought this was a PR to influxdb, so nothing in my last comment applies. Since ops dashboards is managing the initial bucket, adding this param and passing it to the bucket resource makes perfect sense 👍

@m0dular m0dular merged commit 021eb57 into puppetlabs:main Feb 28, 2023
@SimonHoenscheid SimonHoenscheid deleted the shoenscheid_influx_bucket_retention_time branch March 1, 2023 06:48
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

Successfully merging this pull request may close these issues.

3 participants