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
Right now you can use ${dev.MY_SECRET} to reference other secrets in infisical. This is great, however, in my code we have node specific secrets which use the same substitution format. It would be great to have some kind of escape character or option for a specific secret to allow the text ${dev.MY_SECRET} to be passed through so our node specific secrets continue to work.
Why would it be useful?
Allowing the text through so that substitution can be easily done on the server side, as well as the infisical side.
The text was updated successfully, but these errors were encountered:
Feature description
Right now you can use
${dev.MY_SECRET}
to reference other secrets in infisical. This is great, however, in my code we have node specific secrets which use the same substitution format. It would be great to have some kind of escape character or option for a specific secret to allow the text${dev.MY_SECRET}
to be passed through so our node specific secrets continue to work.Why would it be useful?
Allowing the text through so that substitution can be easily done on the server side, as well as the infisical side.
The text was updated successfully, but these errors were encountered: