Skip to content
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

Database migrate option #311

Merged
merged 3 commits into from
Aug 31, 2020
Merged

Conversation

csmithATsquiz
Copy link
Contributor

Make the database migration option available (https://tickets.puppetlabs.com/browse/PDB-4636) to stop a replica system accidentally upgrading the database schema version of a cluster.

@csmithATsquiz csmithATsquiz requested a review from a team as a code owner August 10, 2020 02:37
@puppet-community-rangefinder
Copy link

puppetdb is a class

Breaking changes to this file WILL impact these 4 modules (exact match):
Breaking changes to this file MAY impact these 2 modules (near match):

puppetdb::params is a class

that may have no external impact to Forge modules.

puppetdb::server is a class

that may have no external impact to Forge modules.

puppetdb::server::database is a class

that may have no external impact to Forge modules.

This module is declared in 33 of 575 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.

@austb austb merged commit 0f807f0 into puppetlabs:master Aug 31, 2020
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