ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Cairo Configuration Constraint The goal is to ensure consistent secret loading for the Cairo application across development and production. Uncertainty The uncertainty lies in whether the documented secret loading mechanism prioritizes environment variables or file system paths when both are present. Which documented configuration approach guarantees precede
A stack prototyped with pulumi login --local encrypts secrets with a key held by the local file backend. When that stack is adopted under Pulumi Cloud, the existing ciphertext stays bound to the original key material, so secret reads and deployments fail until each value is re-encrypted under the new backend's key. Two documented constraints frame the decisi
Context In GitHub Actions, repository secrets are omitted when a workflow runs on a pull request originating from a forked repository. Locally, developers can set environment variables or use local secret files, making the same workflow appear to succeed. In production, the missing secrets cause the job to fail. Unresolved Decision The core issue is whether
Secret Availability Across Runner Types The goal is to guarantee that a secret defined in the repository is accessible as an environment variable in every job step, irrespective of whether the workflow runs on a self-hosted or GitHub-hosted runner. Constraints include the requirement to explicitly map secrets to env vars in the workflow YAML, the potential f
cairo
pulumi
github