Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-4636

Add migrate configuration option

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 6.10.0, PDB 5.2.14
    • Component/s: None
    • Labels:
    • Template:
    • Acceptance Criteria:
      • New configuration option migrate in the [database] section
      • document the exit code's meaning in PDB docs
    • Team:
      HA
    • Story Points:
      3
    • Sprint:
      HA Team 2020-02-12, HA Team 2020-02-26, HA Team 2020-03-11
    • Release Notes:
      New Feature
    • Release Notes Summary:
      Hide
      A `[database] migrate` configuration option has been added. When set to `true` (the default), PuppetDB will upgrade the data in the database to the latest format at startup. When `false`, PuppetDB will exit with an error status if the format version is not the one it expects, whether newer or older.
      Show
      A `[database] migrate` configuration option has been added. When set to `true` (the default), PuppetDB will upgrade the data in the database to the latest format at startup. When `false`, PuppetDB will exit with an error status if the format version is not the one it expects, whether newer or older.
    • QA Risk Assessment:
      Needs Assessment

      Description

      The migrate config option (in the [database] section) should determine whether or not PuppetDB will attempt to migrate the Postgres database. When false, it should not attempt migrations, and should exit with status 109 (ascii "m") if the current migration level is not the one it expects. When true (the default), it should behave as it always has, i.e. perform any needed migrations.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              rob.browning Rob Browning
              Reporter:
              austin.blatt Austin Blatt
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support