docs: describe how secrets reach a workspace#25538
Merged
Merged
Conversation
Docs preview📖 View docs preview for |
matifali
reviewed
May 21, 2026
Comment on lines
+75
to
+78
| If you set two file secrets that resolve to the same absolute path (for | ||
| example `~/config` and `/home/coder/config`), only one of them ends up on | ||
| disk; the workspace agent logs a warning to help spot this. Use | ||
| distinct paths to avoid the collision. |
Member
There was a problem hiding this comment.
I guess it would be tricky to catch these collisions when someone is setting the secrets?
Contributor
Author
There was a problem hiding this comment.
Yeah, I don't think there's an easy way to know this ahead of time. We're planning to surface these collisions when the workspace starts before GA.
Comment on lines
+72
to
+73
| > a terminal in your workspace and run `rm <path>`. Rebuilding the workspace | ||
| > also clears stale files when your template recreates the filesystem. |
Member
There was a problem hiding this comment.
Suggested change
| > a terminal in your workspace and run `rm <path>`. Rebuilding the workspace | |
| > also clears stale files when your template recreates the filesystem. | |
| > a terminal in your workspace and run `rm <path>`. Rebuilding the workspace | |
| > may also clears stale files when your template recreates the filesystem. |
Adding may as we can not be sure if a workspace restart recreates filesystem or not.
dylanhuff-at-coder
approved these changes
May 21, 2026
Replace the brief runtime-behavior paragraph with a dedicated section covering when env and file secrets appear in a workspace, what the running workspace sees, and how create/update/delete propagate. Call out that Coder never removes secret files it has written, so deleting a secret or changing its file path leaves the previous file on disk. Co-Authored-By: Coder Agents <noreply@coder.com>
56ec19c to
efd07fd
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace the brief runtime-behavior paragraph with a dedicated section covering when env and file secrets appear in a workspace, what the running workspace sees, and how create/update/delete propagate. Call out that Coder never removes secret files it has written, so deleting a secret or changing its file path leaves the previous file on disk.