Harbor overwrites changes to environment variables

[gbradley]

I'm currently having an issue where I need to modify my environment variables on a branch that I'd like previews for. On initial provision, Harbor takes the environment variables that I've defined in GitHub secrets, which is great.

However if I make a change to the environment via Forge and then push some changes to the PR, Harbor will then overwrite those changes with the ones from GitHub, meaning I have to re-edit them, restart the queue etc.

Is is possible to change the behaviour here, so when updating an existing site, Harbor gives existing variables priority?

[Hannsre]

What we did to prevent this: We removed the updated trigger in the harbor provisioning workflow. We found there to be no reason to re-provision with harbor every time there is some code pushed to the PR.

Not exactly the solution you're looking for, but maybe it helps.

[gbradley]

Thanks for the suggestion, I think you’re right - we’ll probably ignore the synchronize event in the workflow and turn on quick deploy.

[mehrancodes]

Hi @gbradley, maybe Harbor shouldn't touch .env after the first run. Just wondering if there's a reason someone would want to overwrite it every time

[keybrdist]

I have the opposite problem. I need Harbor to rewrite the ENV vars on every build. I would think this should be the default behavior as it would work similar to how a testing environment are built (from 0). Perhaps this should be a HARBOR configuration option?