Skip to content

How to consume a secret from an API call #4088

Discussion options

You must be logged in to vote

Reading the code for the CLI, here I finally figured it out. There's an undocumented parameter called decryptable that, when creating via API and setting it to true, makes it available when running now env pull. I still don't know if this is the correct way of using the API for secret and env variables, but looks like it works now.

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@lucleray
Comment options

Answer selected by mcsdevv
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants