-
-
Notifications
You must be signed in to change notification settings - Fork 165
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
gitlab_monitor got renamed to gitlab_exporter in 12.3 #323
Comments
I'm not sure how we handle deprecated/renamed parameters. Just add an additional parameter Happy to implement this after we figured out how to handle the deprecation! :) |
We've had similar issues come up a few times before. (Hence the section in the README about what major/minor versions this puppet module targets for support). The suggestion you had is one approach we've used, and that works well. (In the past I think we used a The other approach we've used is to coerce one setting into another, like we did with the The first case is used when gitlab changes or removes a parameter, and the latter is used when we deprecate or remove a parameter that was exclusive to this module. |
@baurmatt hope those examples help. I'll keep an eye out to review PR's if you decide to take a shot at it yourself. If you'd rather me do it, just say the word and I'll update and try to release over the weekend. |
Hey @LongLiveCHIEF, thanks for taking a look and pulling out those examples! :) I've tried to implemented it as close as possible to the first PR. |
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Read changelog ;) --> https://docs.gitlab.com/omnibus/update/gitlab_12_changes.html#123
Deprecated. Will be removed in 13.
What are you seeing
gitlab_exporter got renamed to gitlab_monitor.
What behaviour did you expect instead
sys11gitlab::gitlab_exporter should be available
Output log
Any additional information you'd like to impart
The text was updated successfully, but these errors were encountered: