Upgrading a service leads to Rancher losing persistence of environment variables

Question

I am using rancher-compose for upgrading my services. I  have set an environment variable and then I am running the compose command over the terminal. After the upgrade, the environment variable I initialized previously in the UI is not there anymore.

The rancher-compose command that I am using is:

rancher-compose -p [my_stack_name] --url ${RANCHER_ENDPOINT} --access-key ${ACCESS_KEY} --secret-key ${SECRET_KEY} up -d --pull --upgrade --confirm-upgrade
Can anyone help me with this?

Answer 1

when you upgrade, what it will do is, it will do the service match the definition in the compose file that is provided by you. If you are changing things in the UI and not changing your compose file, they will be gone.

I hope that it will let you resolve your problem.