From dafb10e5779f2fbfd85b0cbc021fc4170357282f Mon Sep 17 00:00:00 2001 From: Andrew Chuang Date: Thu, 7 Nov 2024 10:20:15 -0300 Subject: [PATCH 1/5] docs for environment variables in private components --- docs-v2/pages/environment-variables.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs-v2/pages/environment-variables.mdx b/docs-v2/pages/environment-variables.mdx index 5ab87eb184222..4ceabdbcfdc50 100644 --- a/docs-v2/pages/environment-variables.mdx +++ b/docs-v2/pages/environment-variables.mdx @@ -114,6 +114,10 @@ You can reference the value of environment variables using `{{process.env.YOUR_E src="https://res.cloudinary.com/pipedreamin/image/upload/v1708551738/env-vars-feb-2024/env-vars-object-explorer-v2_x9afzl.png" /> + + Private components (actions or triggers) do not have direct access to the same environment execution variables as public components or custom code steps. To use environment variables in private components, add a prop specifically for the variable you need. For sensitive data like API keys, you can [configure the prop as a secret](https://pipedream.com/docs/components/api#props). In your prop configuration, set the value to `{{process.env.YOUR_ENV_VAR}}` to securely reference the environment variable. + + ## Frequently Asked Questions ### What if I define the same variable key in my workspace env vars and project env vars? From 184d4e40c588bd59c9c65fccf9c6b9adbc10413b Mon Sep 17 00:00:00 2001 From: Andrew Chuang Date: Thu, 7 Nov 2024 10:27:35 -0300 Subject: [PATCH 2/5] warning in subscriptions api for git synced projects --- docs-v2/pages/rest-api/index.mdx | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs-v2/pages/rest-api/index.mdx b/docs-v2/pages/rest-api/index.mdx index d6b42a1f78b6e..6337444fde7b0 100644 --- a/docs-v2/pages/rest-api/index.mdx +++ b/docs-v2/pages/rest-api/index.mdx @@ -157,8 +157,8 @@ The response from the request above will have a shape that looks like: Pipedream uses conventional HTTP response codes to indicate the success or failure of an API request: -- Codes in the `2xx` range indicate success. -- Codes in the `4xx` range indicate an error that failed (e.g., a required parameter was omitted). +- Codes in the `2xx` range indicate success. +- Codes in the `4xx` range indicate an error that failed (e.g., a required parameter was omitted). - Codes in the `5xx` range indicate an error with Pipedream's server. ## Accounts @@ -1073,6 +1073,10 @@ DELETE /sources/{id} ## Subscriptions + + The Subscriptions API is currently incompatible with projects that have [GitHub Sync](https://pipedream.com/docs/projects/git) enabled. To [trigger another workflow](https://pipedream.com/docs/code/nodejs#invoke-another-workflow), use `$.flow.trigger` instead. + + ### Listen for events from another source or workflow You can configure a source or workflow to receive events from any number of From efb530b8cd5d4ffdb269d1f886dafb9d2e9003db Mon Sep 17 00:00:00 2001 From: Andrew Chuang Date: Thu, 7 Nov 2024 10:33:16 -0300 Subject: [PATCH 3/5] update description --- docs-v2/pages/environment-variables.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs-v2/pages/environment-variables.mdx b/docs-v2/pages/environment-variables.mdx index 4ceabdbcfdc50..090f5847f7bb6 100644 --- a/docs-v2/pages/environment-variables.mdx +++ b/docs-v2/pages/environment-variables.mdx @@ -115,7 +115,7 @@ You can reference the value of environment variables using `{{process.env.YOUR_E /> - Private components (actions or triggers) do not have direct access to the same environment execution variables as public components or custom code steps. To use environment variables in private components, add a prop specifically for the variable you need. For sensitive data like API keys, you can [configure the prop as a secret](https://pipedream.com/docs/components/api#props). In your prop configuration, set the value to `{{process.env.YOUR_ENV_VAR}}` to securely reference the environment variable. + [Private components](https://pipedream.com/docs/components#using-components) (actions or triggers) do not have access to the same variables as public components or code steps. Add a prop specifically for the variable you need. For sensitive data like API keys, [configure the prop as a secret](https://pipedream.com/docs/components/api#props). In your prop configuration, set the value to `{{process.env.YOUR_ENV_VAR}}` to securely reference the environment variable. ## Frequently Asked Questions From 9f7279cb381a9451c8055ab96d9d6ef0a4ea9515 Mon Sep 17 00:00:00 2001 From: Andrew Chuang Date: Thu, 7 Nov 2024 10:52:40 -0300 Subject: [PATCH 4/5] update --- docs-v2/pages/environment-variables.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs-v2/pages/environment-variables.mdx b/docs-v2/pages/environment-variables.mdx index 090f5847f7bb6..5a4f1c6283d1f 100644 --- a/docs-v2/pages/environment-variables.mdx +++ b/docs-v2/pages/environment-variables.mdx @@ -115,7 +115,7 @@ You can reference the value of environment variables using `{{process.env.YOUR_E /> - [Private components](https://pipedream.com/docs/components#using-components) (actions or triggers) do not have access to the same variables as public components or code steps. Add a prop specifically for the variable you need. For sensitive data like API keys, [configure the prop as a secret](https://pipedream.com/docs/components/api#props). In your prop configuration, set the value to `{{process.env.YOUR_ENV_VAR}}` to securely reference the environment variable. + [Private components](https://pipedream.com/docs/components#using-components) (actions or triggers) do not have access to workspace or project variables as public components or code steps. Add a prop specifically for the variable you need. For sensitive data like API keys, [configure the prop as a secret](https://pipedream.com/docs/components/api#props). In your prop configuration, set the value to `{{process.env.YOUR_ENV_VAR}}` to securely reference the environment variable. ## Frequently Asked Questions From 11559a721722bce82463d03afb84c81deb0b7c70 Mon Sep 17 00:00:00 2001 From: Andrew Chuang Date: Thu, 7 Nov 2024 10:54:14 -0300 Subject: [PATCH 5/5] update --- docs-v2/pages/environment-variables.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs-v2/pages/environment-variables.mdx b/docs-v2/pages/environment-variables.mdx index 5a4f1c6283d1f..d7280377117c7 100644 --- a/docs-v2/pages/environment-variables.mdx +++ b/docs-v2/pages/environment-variables.mdx @@ -115,7 +115,7 @@ You can reference the value of environment variables using `{{process.env.YOUR_E /> - [Private components](https://pipedream.com/docs/components#using-components) (actions or triggers) do not have access to workspace or project variables as public components or code steps. Add a prop specifically for the variable you need. For sensitive data like API keys, [configure the prop as a secret](https://pipedream.com/docs/components/api#props). In your prop configuration, set the value to `{{process.env.YOUR_ENV_VAR}}` to securely reference the environment variable. + [Private components](https://pipedream.com/docs/components#using-components) (actions or triggers) do not have direct access to workspace or project variables as public components or code steps. Add a prop specifically for the variable you need. For sensitive data like API keys, [configure the prop as a secret](https://pipedream.com/docs/components/api#props). In your prop configuration, set the value to `{{process.env.YOUR_ENV_VAR}}` to securely reference the environment variable. ## Frequently Asked Questions