Here is how to replicate the issue:
Go to doppler and make a personal config (but same issue with base configs), and inherit a bunch of secrets. Reload the page, just to make sure they show up there.
Go to the project you have set up with that config, run doppler secrets and see that everything is there.
Run doppler run --printenv and see that some secrets are missing.
This is breaking my docker compose setup (and also staging when I update configs, I am afraid to push to prod for this reason).
Iâve had luck adding and removing uninherited secrets and then saving them, which might be triggering some sort of refresh on the backend, but the behavior I would expect is:
- Add an inherited config in the UI
- Be in the âunsaved changesâ state
- Once you save it, run the refresh that allows the secrets to be propagated.
The big thing is, adding inherited configs seems like it should need confirmation to be set, it doesnât, and it doesnât propagate. This is a pretty serious bug, because if I didnât figure out the âmake another change that needs to be saved,â I wouldnât be able to make safe changes in production.
My workaround is to add a dummy SAVE_STUB to each base config, and every time I make a change to the inherited config, change the value of it and click save. This sucks tho, and If I forget then I could break prod.
Thanks!
