-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
1
-
False
-
None
-
False
-
Yes
-
MGDAPI - Sprint 25, MGDAPI - Sprint 26
WHAT
The addon parameters secret is created in the operators namespace. This secret will have different names depending on how hive installs it. If the internal addon is installed the secret name is addon-managed-api-service-internal-parameters while in the production version this is addon-managed-api-service-parameters.
We need to update the GetParameterByInstallType to handle the different secret names.
HOW
The GetName is used to get the name of the secret this will need to use both the installation type and namespace to get the correct secret name.
Following up on Jims comment below, could we find the secret by a label possibly? Or something that would generically identify the secret.
Filter by label first and then identify the addon secret by regex. `hive.openshift.io/managed=true`
TESTS
Unit tests need to be added for both functions.
Test should include different namespace and different secret names. Do reference MGDAPI-3923 as that would will add a new namespace that needs to be covered.
DONE
- operator can get the addon parameters secret for that installation type and namespace.
- functions are fully unit tested.
- blocks
-
MGDAPI-4022 Addon secret missing alert and error
- Closed
- is triggered by
-
MGDAPI-3764 Feature request to enable custom SMTP configuration for RHOAM deployment
- Closed
- mentioned on