Skip to content

all parameters on main class #110

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

Conversation

SimonHoenscheid
Copy link
Contributor

  • move subclass parameters with defaults to main class
  • lookup default in main class
  • copy parameter documentation if available

@SimonHoenscheid SimonHoenscheid requested a review from a team as a code owner September 5, 2022 13:56
@m0dular
Copy link
Contributor

m0dular commented Sep 15, 2022

@SimonHoenscheid We have a couple of duplicate parameters that are tripping up the validfation.

pdk (ERROR): puppet-syntax: The parameter 'manage_reports_autovacuum_cost_delay' is declared more than once (the parameter list (file: /home/adrian/repos/puppetlabs-pe_databases/manifests/init.pp, line: 49, column: 14))
pdk (ERROR): puppet-syntax: The parameter 'factsets_autovacuum_vacuum_scale_factor' is declared more than once (the parameter list (file: /home/adrian/repos/puppetlabs-pe_databases/manifests/init.pp, line: 50, column: 24))

@SimonHoenscheid SimonHoenscheid force-pushed the shoenscheid_all_parameters_on_main_class branch from e620001 to 8e7e59b Compare October 7, 2022 14:21
* lookup default in main class
* copy parameter documentation if available
@SimonHoenscheid SimonHoenscheid force-pushed the shoenscheid_all_parameters_on_main_class branch from 8e7e59b to 8c52a47 Compare October 7, 2022 14:30
@SimonHoenscheid
Copy link
Contributor Author

@m0dular I fixed these issues

@SimonHoenscheid
Copy link
Contributor Author

@m0dular @MartyEwings please review again

@m0dular
Copy link
Contributor

m0dular commented Nov 4, 2022

Hi, sorry about the delay on this one. We have another PR #112 that should be merged soon that will be incompatible with this one. We have postgres tuning related stuff in the product at this point, so the postgresql_settings classes in this module are mostly redundant.

It might not be well documented at this point, but the database profile class does some calculations to come up with the postgres settings, which should also be configurable if needed. For example, puppet_enterprise::profile::database::work_mem for work_mem.

If there's anything in this PR that isn't related to the deprecated classes, could you rebase it onto #112? Thanks.

@SimonHoenscheid
Copy link
Contributor Author

I think it makes sense to close this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants