Heroku Sync overwrites/deletes HEROKU_BUILD variables

Need Help
1

Hi,

I’m having a problem with a sync to Heroku overwriting variables that are populated directly from Heroku. I know Doppler handles some internal Heroku vars, but it doesn’t seem to handle HEROKU_BUILD_COMMIT and HEROKU_BUILD_DESCRIPTION.

Is there a way to highlight to Doppler to leave some vars alone, so I can stop this?

Otherwise/also is there a way to highlight this issue with Doppler without having a support contract?

Thanks,

Mark

2

Hi Mark!

Thanks for surfacing this, and you can always open a support ticket with us. Heroku’s documentation states that config vars not created by Heroku should not start with HEROKU_ but they do not currently enforce this, which is why we don’t block it for configs with Heroku syncs attached.

Typically, we only enforce limits like that when the third party service has it as a hard requirement. I’ll bring this up with our engineering team, though, as it would be good to have it more cleanly documented on our side.

3

Thanks for the reply.

I just wanted to clarify some things as I wasn’t 100% sure from your reply if you’d understood my issue correctly and I realised that my original message was a little unclear.

HEROKU_BUILD_COMMIT and HEROKU_BUILD_DESCRIPTION are set by Heroku in my Heroku env vars. We do not have these populated in Doppler. When a sync occurs Doppler is deleting these env vars from Heroku. I don’t believe this should happen/would like to find a way to stop this happening.

Thanks,

Mark

4

@Ryan_Hanson Just wanted to check you’d seen my reply and passed that on too.

It seems from your response that this will require internal changes and that there’s no way for me to do anything to tell the system to leave these vars alone?

If so, what’s my best way to track when a change may come?

Thanks,
Mark