docs: add --env-file / -e flag documentation and examples#46
Merged
seanseannery merged 1 commit intomainfrom Mar 9, 2026
Merged
docs: add --env-file / -e flag documentation and examples#46seanseannery merged 1 commit intomainfrom
seanseannery merged 1 commit intomainfrom
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.
Key Changes
--env-file/-erow to the flags reference table and a new "Injecting Secrets with--env-file" subsection inREADME.mdcovering usage,.ops_secrets.envdefault, env-scoped keys,.gitignorerecommendation,--dry-runcaveat, and flag-position constraint-eusage comment blocks toOpsfile_baremetal,Opsfile_local, andOpsfile_azureexamples showing how to inject credential-like variablesdocs/site/index.htmlflags table and "Secrets-Safe by Design" feature card to mention the-eflagWhy do we need this?
Follow-on documentation for the
--env-filefeature shipped in #45. User-facing docs and examples were not included in that PR.New modules or other dependencies introduced
None.
How was this tested?
Documentation-only changes — no Go files modified.