Document the Compose security model#404
Merged
Merged
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The security guide added in #388 covers the osls CLI but says nothing about Compose, whose documentation lives in this repository. This adds a security model section to the Compose guide covering the Compose-specific shape of the same concerns: configurations can be JavaScript or TypeScript files that execute on load, environment-resolved values flow into the command line parameters of the spawned osls processes, and service outputs persist in the local state directory and the remote state bucket, so both deserve the same protection as other deployment artifacts. The section links back to the main security guide rather than repeating it.