Update upgrade documentation, manual steps section
Because the upgrade process has changed, the manual step have changed a bit too.
Make convert node group application optional
This will allow the convert plan to be used to update trusted certificate extensions without enforcing node group changes. Such a capability is useful for upgrading from 2018.1 to 2019.7
Add convert compatibility for PE 2018.1
Puppet 5, doesn't have the `puppet ssl` command.
New style compilers don't have a peadm_role cert extension anymore; they only have a pp_auth_role.
Update classification earlier in the upgrade
So that compilers classify successfully and can run Puppet
Switch to run_command for compiler service stops
When using the orchestrator transport there is a problem with the built-in service task when the orchestrator is upgraded but the pxp-agents are not. Switching to run_command and `systemctl stop` during this time avoids the problem.
Don't re-cert compilers until master is upgraded
Otherwise, the certs potentially can't be signed due to having authorization extensions.
(maint) Update Puppet VS Code Extension ID
This commit updates the configuration file to point to the official Puppet VS Code Extension `puppet.puppet-vscode`
Merge pull request #100 from jpogran/maint-update-puppet-vscode-id
(maint) Update Puppet VS Code Extension ID
Don't start Puppet re-issuing certs if its stopped
If it was stopped before, it should still be stopped after.
Use run_command for compatibility
We now use this plan at a time when the master is 2019.x but agents could be 2018.x. So, make it compatible.
Shut down puppetserver before rm'ing files
Otherwise it seems there's a chance it'll re-create files we need to be absent.
Merge pull request #102 from vchepkov/rhel8-python
use platform-python on RHEL8
Merge pull request #101 from puppetlabs/upgrade-from-2018
Upgrade from 2018
Tested upgrade from 2019.7 locally with success.
Merge pull request #104 from bryanjbelanger/patch-1
Update validate_version.pp
Add token_file flag for upgrade
So that users who keep token files in a non-standard location can still run the upgrade plan (starting with 2019.8 and newer)
Add util plan to clean up pe.conf on PG nodes
If a PG node has the wrong entry for puppet_master_host or database_host, then running puppet-enterprise-installer won't upgrade PostgreSQL as needed. The pe.conf on PG nodes is effectively inert most of the time, so if it gets out of date there's nothing to fix it. This optional util plan will ensure the pe.conf has the minimum required correct values. This util plan may be integrated into the upgrade plan at a later date.
This will be the last manual CHANGELOG file, per https://confluence.puppetlabs.com/display/ECO/Self-Service+Module+Release+Process