boardx / boardx/workspacex

fix(deploy): preserve readable CA permissions when regenerating runtime

Open
#3,584 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
1h 7m
Merged PRs (30d)
969

Description

Production readiness failed because an existing private runtime certificate directory remained mode 0700 after writeRuntimeBundle reused it. The generated Redis CA files therefore could not be read by the non-root API and Agent containers. Ensure the public CA mount directories are normalized to 0755 and CA files to 0644 on every regeneration, while secret files remain 0600. Add a filesystem-mode regression test that starts from pre-existing private directories.\n\nThis is an ad-hoc production reliability fix.

Contributor guide

No contributing guide indexed for this repository

Research direction

Locate the writeRuntimeBundle entry point and the filesystem-mode test area. Reproduce regeneration with pre-existing private directories, then verify public CA mount directories are 0755, CA files are 0644, and secret files remain 0600 for the non-root API and Agent containers.

Written by the indexing model from the issue text.

Assessment

Tech stack
redis, typescript
Domain
devops, infrastructure, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.