You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The environment variable should be deployed under the check itself with the value bar#baz. When deploying it as an environment variable it's visible it's cropped off. When using a secret not directly but when entered e.g. into a password field the string is noticeable shorter.
What is actually happening?
Said environment variable is however saved as bar. So essentially cropped off at the #.
Any additional comments?
I've noticed the same in the Checkly UI when trying to update the environment variable. At first it appears to be saved as bar#baz but when saving and reloading it again is cropped at bar.
This seems to correlate with the release of the Secrets for sensitive data release. Of course this is just a guess.
The text was updated successfully, but these errors were encountered:
@tdeekens I can't reproduce the issue, having an environment variable (clear, locked and/or secret) with a value as foo#bar doesn't cause any trouble on my end.
Node.js version
22
NPM version
10
@checkly/cli version
4.9.1
Steps to reproduce
Create any check (API or Browser). This check must contain an environment variable (secret or not) such as:
What is expected?
The environment variable should be deployed under the check itself with the value
bar#baz
. When deploying it as an environment variable it's visible it's cropped off. When using a secret not directly but when entered e.g. into a password field the string is noticeable shorter.What is actually happening?
Said environment variable is however saved as
bar
. So essentially cropped off at the#
.Any additional comments?
I've noticed the same in the Checkly UI when trying to update the environment variable. At first it appears to be saved as
bar#baz
but when saving and reloading it again is cropped atbar
.This seems to correlate with the release of the Secrets for sensitive data release. Of course this is just a guess.
The text was updated successfully, but these errors were encountered: