This website uses cookies to ensure you get the best experience.
Learn more.
A build executes pull-request code from external contributors. The production deployment credential is currently available in every build. Which change best limits the risk of untrusted build execution?
Published
- Mask the credential in the console and assume code cannot use it.
- Keep production secrets in every build and ask contributors not to print them.
- Give every pull request administrator privileges to avoid permission failures.
- Separate untrusted validation from privileged deployment and provide each stage only the permissions and secrets it actually needs.
Comments — 0
Sign in to comment