New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Environment variable is not updated after subsequent deploys #1833

Closed

AlexanderMoiseev opened this issue Apr 27, 2021 · 1 comment

Labels

bug

Collaborator

AlexanderMoiseev commented Apr 27, 2021 •

edited

Loading

Environment var is not updated after subsequent deploys

Steps to reproduce the behavior:
First way to reproduce

deploy an app with 'yarn resolve-cloud deploy -n app-1 --env VAR=env_v1' - ( env set correctly for the first time )
deploy an app again with the same name and different env value 'yarn resolve-cloud deploy -n app-1 --env VAR=env_v2'
run yarn resolve-cloud environment list
Result - env is not updated

Second way to reproduce

deploy an app with 'yarn resolve-cloud deploy -n app-1' ( don't provide env)
set env variable within existing deployment with ' yarn resolve-cloud environment set 'deployId' VAR=env_v1
remove this env from deployment with 'remove' command
deploy an app with with the same name and provide an env variable 'yarn resolve-cloud deploy -n app-1 --env VAR=env_v2'
Result - env is not updated

Expected behavior
env is updated after these steps

Node.js Version [e.g. 12.18.1]
ReSolve Version [e.g. 0.28.2]

Lykoi18 added the bug label

Collaborator

Lykoi18 commented Apr 30, 2021

Fixed in 0.30.1

Lykoi18 closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment