in setup.sh, setting env vars via --update-env-vars is not always idempotent, it fails if a variable doesn't exist about emblem

[grayside]

Next step: Reproduce the issue by examining an end-to-end Emblem setup deploy.

[glasnt]

setup.sh should only be run once, on new projects; the difference between --update-env-vars and --set-env-vars on creation of services should be identical.

If there's existing services in an environment, resetting configurations through the setup.sh script isn't in scope. Reapplying terraform to reassert state, but emblem chooses to use scripts for the cloud run services.

To make a more idempotent environment, it would be a feature/refactor to move all setup into terraform.

(I would now close this issue, but I don't have permissions)