Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Let DBaaS enabled after upgrade when it is enabled using PERCONA_TEST_DBAAS environment variable

Description

User story:
When user has DBaaS enabled using PERCONA_TEST_DBAAS=1 it should be enabled after upgrade even if the environment variable PERCONA_TEST_DBAAS is now deprecated.

Acceptance criteria:
User can access DBaaS after upgrade when it was enabled using PERCONA_TEST_DBAAS env var.

Suggested implementation:
Update pmm-update:

  • check if env var PERCONA_TEST_DBAAS is set to 1 in the beginning of the upgrade and if it is, include environment=ENABLE_DBAAS=1 into pmm.ini file that descirbes how pmm-managed is run

  • change the way we check for dbaas-controller running - use supervisorctl status and grep

How to test:
Run pmm using docker container with PERCONA_TEST_DBAAS=1 env, try to upgrade to latest dev and see if DBaaS is still enabled after upgrade is done.

How to test

None

How to document

None

Activity

Former user 
April 22, 2021 at 9:51 AM

Flag added

Blocked by . I can merge pmm-update part only when DBaaS flag is merged. There was a change in environment variable name for dbaas enabling.

Won't Do

Details

Assignee

Reporter

Priority

Components

Needs QA

Story Points

Sprint

Parent

Created April 16, 2021 at 10:39 AM
Updated November 13, 2024 at 9:55 AM
Resolved April 22, 2021 at 11:27 AM