-
Bug
-
Resolution: Done
-
Major
-
RHODS_1.25.0_GA
-
False
-
None
-
False
-
Release Notes
-
Testable
-
No
-
-
-
-
-
-
-
1.26.0
-
No
-
-
Bug Fix
-
Done
-
No
-
Yes
-
None
-
-
-
RHODS 1.26
Description of problem:
when you upload a secret yaml file, the values do not get decoded before storing them into the Secret. It means, the values get re-encoded. If you add a new environment variable in the workbench using the Key/Value method, it doesn't happen.
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
- create a DS project
- create a workbench and add env variables by uploading a Secret (yaml format)
- fill the remaining workbench data
- submit the workbench creation
- check the Secret which gets created in OpenShift
Actual results:
values under "data" section of the Secret get encoded twice: the yaml file has already the values encoded
Expected results:
values under "data" section of the Secret do not get re-encoded
Reproducibility (Always/Intermittent/Only Once):
Always
Build Details:
RHODS 1.25
Workaround:
decode the values when using the environment variables in Jupyter
Additional info:
- is caused by
-
RHODS-5932 [DSG] missing upload option for creating an environment variable as Secret
- Closed
- mentioned on