Skip to content

feat: Making clearer that env vars are shared along with source code#2414

Open
mtrunkat wants to merge 3 commits intomasterfrom
feature/env_vars
Open

feat: Making clearer that env vars are shared along with source code#2414
mtrunkat wants to merge 3 commits intomasterfrom
feature/env_vars

Conversation

@mtrunkat
Copy link
Copy Markdown
Member

@mtrunkat mtrunkat commented Apr 9, 2026

This was not mentioned at the right places, so adding it to the publication and env vars sections.

@mtrunkat mtrunkat requested a review from fnesveda April 9, 2026 14:13
@mtrunkat mtrunkat requested a review from TC-MO as a code owner April 9, 2026 14:13
Copilot AI review requested due to automatic review settings April 9, 2026 14:13
@mtrunkat mtrunkat added the adhoc Ad-hoc unplanned task added during the sprint. label Apr 9, 2026
@github-actions github-actions bot added the t-management Issues with this label belong to the CTO or engineering managers. label Apr 9, 2026
@apify-service-account
Copy link
Copy Markdown

Preview for this PR was built for commit 3b55fbd and is ready at https://pr-2414.preview.docs.apify.com!

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds documentation clarifying that publishing an Actor makes its source code and non-secret environment variables visible on the Actor detail page, and explains how the “Hide source files from Actor detail” setting affects this.

Changes:

  • Add a “Source code visibility” section to the Actor publishing guide.
  • Add a caution admonition to the environment variables page about visibility for public Actors.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
sources/platform/actors/publishing/publish.mdx Documents default public visibility of source files and non-secret env vars after publishing, and how to hide them in Console settings.
sources/platform/actors/development/programming_interface/environment_variables.md Adds a caution explaining that non-secret env vars can be publicly visible for published Actors and how the hide-source setting affects them.

Comment thread sources/platform/actors/publishing/publish.mdx Outdated
@apify-service-account
Copy link
Copy Markdown

Preview for this PR was built for commit eb26d8b and is ready at https://pr-2414.preview.docs.apify.com!

Copy link
Copy Markdown
Contributor

@TC-MO TC-MO left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cleaned up prose & rephrased both additions for consistency

Comment on lines +121 to +127
:::caution Visibility of environment variables in public Actors

When you [publish your Actor](/platform/actors/publishing/publish), environment variables not marked as **Secret** in Apify Console are visible to anyone on the Actor detail page along with the source code. If you enable **Hide source files from Actor detail** in the Actor's **Settings**, environment variables not marked as **Secret** in Apify Console are hidden as well.

Secret environment variables are never exposed on the Actor detail page regardless of this setting. Always mark sensitive values as **Secret**.

:::
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
:::caution Visibility of environment variables in public Actors
When you [publish your Actor](/platform/actors/publishing/publish), environment variables not marked as **Secret** in Apify Console are visible to anyone on the Actor detail page along with the source code. If you enable **Hide source files from Actor detail** in the Actor's **Settings**, environment variables not marked as **Secret** in Apify Console are hidden as well.
Secret environment variables are never exposed on the Actor detail page regardless of this setting. Always mark sensitive values as **Secret**.
:::
:::caution Visibility of environment variables in public Actors
When you [publish your Actor](/platform/actors/publishing/publish), environment variables not marked as **Secret** in Apify Console are visible to anyone on the Actor detail page alongside the source code. Enable **Hide source files from Actor detail** in the Actor's **Settings** to hide both.
Apify Console never exposes secret environment variables on the Actor detail page, regardless of this setting. Always mark sensitive values as secret
:::

Comment on lines +59 to +64

## Source code visibility

When you publish an Actor, its source code files and non-secret [environment variables](/platform/actors/development/programming-interface/environment-variables) are publicly visible by default on the Actor detail page.

To hide them, go to your Actor's **Settings** tab in Apify Console and check **Hide source files from Actor detail**. Secret environment variables are never exposed regardless of this setting.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Source code visibility
When you publish an Actor, its source code files and non-secret [environment variables](/platform/actors/development/programming-interface/environment-variables) are publicly visible by default on the Actor detail page.
To hide them, go to your Actor's **Settings** tab in Apify Console and check **Hide source files from Actor detail**. Secret environment variables are never exposed regardless of this setting.
## Source code visibility
When you publish an Actor, its source code files and non-secret [environment variables](/platform/actors/development/programming-interface/environment-variables) are publicly visible by default on the Actor detail page.
To hide them, go to your Actor's **Settings** tab in Apify Console and check **Hide source files from Actor detail**. Apify Console never exposes secret environment variables regardless of this setting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

adhoc Ad-hoc unplanned task added during the sprint. t-management Issues with this label belong to the CTO or engineering managers.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants