-
Notifications
You must be signed in to change notification settings - Fork 368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for (external) secrets in sync scripts #763
Labels
enhancement
New feature or request
Comments
Wouldn't "support for (external) secrets in sync scripts" be a clearer title? |
bastienbeurier
changed the title
Support for env variables in sync scripts
Support for (external) secrets in sync scripts
Jul 12, 2023
@khaliqgant here's a proposed design. |
khaliqgant
added a commit
that referenced
this issue
Sep 12, 2023
khaliqgant
added a commit
that referenced
this issue
Sep 12, 2023
khaliqgant
added a commit
that referenced
this issue
Sep 12, 2023
khaliqgant
added a commit
that referenced
this issue
Sep 13, 2023
khaliqgant
added a commit
that referenced
this issue
Sep 13, 2023
khaliqgant
added a commit
that referenced
this issue
Sep 18, 2023
khaliqgant
added a commit
that referenced
this issue
Sep 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The use-case here is a sync script requiring the use of a bot token. This bot token is different per env (dev vs. prod). Given the sensitive nature of the token, it's best not to have it in clear in the sync script. The user asked to set this env variable in the Nango UI.
Implemented Features
getEnvironmentVariables
method in the sdk for Sync/Action scripts only which returns the{ name: string; value: string }
pairgetEnvironmentVariables
method isn't awaited in a sync scriptThe text was updated successfully, but these errors were encountered: