Skip to content

Honor mode on materialized configs/secrets#14

Merged
flaticols merged 1 commit into
mainfrom
feat/honor-mode
Jun 21, 2026
Merged

Honor mode on materialized configs/secrets#14
flaticols merged 1 commit into
mainfrom
feat/honor-mode

Conversation

@flaticols

Copy link
Copy Markdown
Owner

Small secret/config polish (container-compose only; no ComposeKit change).

  • content:/environment: configs & secrets are materialized to a temp file we own, so we now chmod them to the requested mode (e.g. 0440).
  • uid/gid still need root → stay warned. mode on a file: source is warned (we don't own the file).
  • parseMode accepts 0440, 0o440, and a plain decimal whose value is already the mode bits (YAML may decode 0440 to 288 = 0o440). Unit-tested. 33 tests pass.

content:/environment: configs & secrets are written to a temp file, so we can
chmod them to the requested mode (e.g. 0440). uid/gid still need root and stay
warned; mode on a file: source is warned (not ours to chmod). Adds a parseMode
unit test (octal / 0o / decimal-as-bits).
@flaticols flaticols merged commit 58aba12 into main Jun 21, 2026
1 check passed
@flaticols flaticols deleted the feat/honor-mode branch June 21, 2026 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant