Var created in UI but unavailable in envkey-source

[thomasLeclaire]

Hello!
I got a really strange issue today creating some new vars.
Everything ok in the envkey UI, change commited, available on UI from others users. When I export the full env, the new variable is available.

However, on a specific env (the Development one), when checking envkey-source, the var is not available when it is available on the others one like staging or prod.

I renamed the var to "BLA", still unavailable.
I recreated an other var with the original problematic name and values : this new one is available. The problematic BLA one still unavailable, still only on the Development env.

I modify this BLA var to a different value : it's now available!
I remodify to the hypothetic problematic value : it's available..

I use the UI feature to rollback to initial value (which is yet the same) : it's unavailable again..

I know it's for sure impossible to reproduce on your side, and probably impossible to investigate, but I thought it can be interesting to say, at least if anyone has a such issue in the future!

[danenania]

Thanks for reporting this and for all the details. What flags are you passing to envkey-source when loading in development? Are you using any of --watch / w, --cache / -c, or --mem-cache / -m?

[thomasLeclaire]

I didn't use any flags.
just ENVKEY=XXX envkey-source

tried to removed the potential local .envkey folder, but not better
tried to use --force flag but not better

[danenania]

Thanks @thomasLeclaire. If you see it again, could you try running envkey-source with the --verbose flag? Our hypothesis currently is that the envkey-source requests you saw issues with were failing to hit the primary API endpoint for some reason and then failed over to an eventually consistent backup endpoint that was slow to update. The --verbose output shows whether the primary or a failover is being used, so it could help to confirm that's what is happening. While it should be a very rare scenario, it could cause results like you describe.

[thomasLeclaire]

in fact I didn't removed the problematic var and so I can still observe it at this time.
and sounds I hit correctly the primary API endpoint.

using ENVKEY environment var
loaded ENVKEY
Attempting to load encrypted config from url: https://api-v2.envkey.com/fetch?fetchServiceVersion=2&envkeyIdPart=XXXX&clientName=envkey-source&clientVersion=2.4.1&clientOs=darwin&clientArch=amd64
Parsing and decrypting response...
export XXXXXXX

[adityapatadia]

We are also facing the same issue and downgrading envkey-source resolved the problem. Definitely something is wrong with new version.

[danenania]

Hi @adityapatadia which version were you on where you saw the issue and which did you downgrade to?

[adityapatadia]

Nodejs 2.5 has definitely issue. For our ease we downgraded to 2.1 and it works fine.—Regards,Aditya PatadiaOn 02-Aug-2023, at 10:36 PM, Dane Schneider ***@***.***> wrote: Hi @adityapatadia which version were you on where you saw the issue and which did you downgrade to? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[danenania]

@adityapatadia Do you have any .env files either in the project root directory or a higher-level directory? There were some changes to how .env files that don't include an ENVKEY were handled in 2.4.0 - https://github.com/envkey/envkey/releases/tag/envkeysource-v2.4.0

Previously they were ignored, but now they are applied and will take precedence over EnvKey vars if set. This could potentially cause the behavior you're seeing.

[adityapatadia]

Does this mean that if there is env file with only ENVKEY in it, then no other variables will get populated? If yes this is a big breaking change.—Regards,Aditya PatadiaOn 03-Aug-2023, at 4:18 AM, Dane Schneider ***@***.***> wrote: @adityapatadia Do you have any .env files either in the project root directory or a higher-level directory? There were some changes to how .env files that don't include an ENVKEY were handled in 2.4.0 - https://github.com/envkey/envkey/releases/tag/envkeysource-v2.4.0 Previously they were ignored, but now they are applied and will take precedence over EnvKey vars if set. This could potentially cause the behavior you're seeing. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[danenania]

No @adityapatadia, there has been no change to how an env file with just an ENVKEY in it is handled.

[aqidd]

Encounter the same problem today. One of the env variables is not detected in production, but available in development. We're using the latest 2.4.3 version