-
Bug
-
Resolution: Done
-
Major
-
fuse-7.10-GA
-
None
-
False
-
False
-
%
-
+
-
Automated
-
When I have a running integration with some custom environments, and I delete one of them or change the name of some of them in UI, after rebuilding, the integration contains also the old environments.
Integration ENVs
ENV1: VALUE1 ENV2: VALUE2 ENV4: VALUE4
After redeploying of integration (deleted ENV2 and changed the name of ENV4 to ENV4NAMEUPDATED in the UI), the integration pod contains ENVs:
ENV1: VALUE1 ENV2: VALUE2 ENV3: VALUE3 ENV4: VALUE4 ENV4NAMEUPDATED: VALUE4
- is caused by
-
ENTESB-16398 Ability to set custom environment variables on the integration deploymentconfig
- Closed