Adding catalog_inputs to the pg_repack scheme for PE 2019.8.0+

[coreymbe]

Adding catalog_inputs to the pg_repack scheme for PE 2019.8.0+.

[puppet-community-rangefinder]

pe_databases::maintenance::pg_repack is a class

that may have no external impact to Forge modules.

This module is declared in 0 of 576 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.

[MartyEwings]

Would it be possible to add this table to the existing catalogs tables cron job ?

[coreymbe]

@MartyEwings :: I can, but doing so will cause the catalogs repack to fail pre 2019.8.

tail /var/log/puppetlabs/pe_databases_cron/catalogs_repack.log
ERROR: pg_repack failed with error: ERROR: relation "catalog_inputs" does not exist

facter -p pe_server_version
2018.1.18

[MartyEwings]

@MartyEwings :: I can, but doing so will cause the catalogs repack to fail pre 2019.8.

tail /var/log/puppetlabs/pe_databases_cron/catalogs_repack.log

That table came in in 2019.8.2 so we will have to have a conditional that exempts it prior to this release as we have to support 2019.8.x

There is a conditional nick points to as an example in the comments of the previous PR #47

that should do the job

[coreymbe]

Ahh, I see now. Okay that makes more sense, I'll get that fixed up. 👍🏽

[MartyEwings]

Looks good to me!

[MartyEwings]

tested and is working on 2021.1 as well