[PDB-3993] Add --upgrade-and-quit or similar for unattended multi-version upgrades Created: 2018/07/30  Updated: 2018/10/22  Resolved: 2018/09/06

Status: Closed
Project: PuppetDB
Component/s: None
Affects Version/s: None
Fix Version/s: PDB 5.2.6, PDB 6.0.0

Type: Improvement Priority: Normal
Reporter: Rob Browning Assignee: Rob Browning
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Team: PuppetDB
Release Notes: New Feature
Release Notes Summary: (Note: this feature was added to 5.2.x and to 6.0.0, so we have two sets of release notes depicted below. The 5.2.x notes should go on the 5.2.x branch, and then we'll merge them up to master (or 6.0.x), and then
the 6.0 notes should be added to master (or 6.0.x).)

*** For 6.0.0 ***

- A `help` subcommand has been added to display usage information to standard output.

- If an invalid command is specified, usage information will now be printed to standard error, not standard output.

*** For 5.2.x ***

[versioning]: ./versioning_policy.html#upgrades
[multiple-major-upgrades]: ./upgrade.html#upgrading-across-multiple-major-versions

## 5.2.?

### New features

- An `upgrade` subcommand has been added that should be useful for cases where you want to upgrade across multiple major versions without skipping major versions (as per the [versioning policy][versioning]). See [these notes [multiple-major-upgrades] for additional information.

QA Risk Assessment: Needs Assessment


So that someone on a much older version of pdb can just run the updates in sequence without having to try to guess when an upgrade is complete.

Generated at Thu Nov 14 12:07:06 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.