Different Namespaces' PgConfigs make Major Version Upgrade fail
Summary
When creating a Major Version Upgrade, the Target Postgres Configuration
field shows all PgConfigs, no matter their Namespace. Since all PgConfigs appear, it is possible that the User chooses a PgConfig of a different Namespace. This makes the Operation fail because the PgConfig could not be found (since it is on another Namespace).
Steps to reproduce
- Create a cluster on any Postgres Version but 14.0
- Create a Major Version Upgrade Operation.
- Choose 14.0 as Target Postgres Version, and see that other Namespaces' PgConfigs appear on the Target Postgres Configuration field.
- Select a PgConfig that does not exist on your Namespace and try to create the Operation.
Expected Behaviour
The PgConfigs that appear on the Target Postgres Configuration
field should not make the Operation fail.
Possible Solution
The PgConfigs on the Target Postgres Configuration
field should be filtered, and only those on the current Namespace should appear.
Environment
- StackGres version: 1.0.0-RC1
Edited by Olesya Saletska