Skip to content

Sec Decomposition skip tests for pre-decomposition BG migrations

Gregory Havengarequested to merge
ghavenga-sec-decomp-skip-bg-spec into master

What does this MR do and why?

For sec-decomposition, it has been determined that the safest way to enact the decomposition is to ensure that all BBM's that depend on the tables that will be decomposed should be finalised prior to rollout. This avoid the complexity of managing transferred or interrupted BBM's, and means we can avoid making modifications to the BBM's or their spec to make them work and account for the new database setup, as they should be resolved before the rollout.

The spec for these migrations has various issues with the new Sec database connection as the database analyser detects that the wrong connection is used for some interactions. Rather than solve this, it is simpler to skip these tests should we detect that a Sec database is configured.

This MR will allow these migrations to pass a CI test run where a Sec database is configured, but we need to ensure they are ALL finalised prior to the Sec rollout.

This change won't have any affect on our currently configured CI pipelines, but we will see all of these tests skip in a Sec enabled pipeline, which we are validating in this MR.

Related Issues

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Edited by Gregory Havenga

Merge request reports