Ilya Sytchev

All three environments (dev: Vagrant, prod: AWS, CI: Travis) should be updated in sync. We may have to replace Travis with another CI system but I don't think it's necessary...

This will not be an issue when #2741 is addressed.

Still an issue as of v1.6.9.1

Still an issue in v1.6.9.1

Hey @GSPatton, I've used `pg_roles` because it's already used extensively in `role.pp`. Also, another "legacy" view `pg_shadow` was used in a recently merged PR: https://github.com/puppetlabs/puppetlabs-postgresql/pull/1347/files. How is this case different?

I see, thanks. I'm trying to install some tools, customize some `.loc` files, as well as `job_conf.xml`. What would be the best approach?

OK, thanks. I should have mentioned that I also need to produce a galaxyFS archive that could be used in our private Cloud Launch instance along with a custom galaxyIndices...

Thank you for looking into this. The deprecation message is the only additional output I've received. How can I obtain a full stack trace?

Here's a full sample output: ``` # /opt/puppetlabs/puppet/bin/librarian-puppet Top level ::CompositeIO is deprecated, require 'multipart/post' and use `Multipart::Post::CompositeReadIO` instead! Top level ::Parts is deprecated, require 'multipart/post' and use `Multipart::Post::Parts` instead!...

Also, installation is broken with Puppet 6: ``` 2022/06/09 17:27:52 GCEMetadataScripts: startup-script: + /opt/puppetlabs/puppet/bin/gem install librarian-puppet -v 3.0.1 --no-document 2022/06/09 17:27:53 GCEMetadataScripts: startup-script: ERROR: Error installing librarian-puppet: 2022/06/09 17:27:53 GCEMetadataScripts:...