Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Epic: Support build-time credential injection #959

Closed
3 tasks
vdice opened this issue Mar 24, 2020 · 1 comment
Closed
3 tasks

Epic: Support build-time credential injection #959

vdice opened this issue Mar 24, 2020 · 1 comment
Labels
enhancement New code incoming!

Comments

@vdice
Copy link
Member

vdice commented Mar 24, 2020

There are use cases where Porter authors would like a way to inject credentials at build-time (rather than the currently supported run-time injection). For instance, if a mixin supports extended configuration and this configuration may need credentials to run. (See getporter/helm2-mixin#61 for an example)

To enable this, we'd need the following features added:

  • Porter build takes an optional credential set, porter build -c cred

  • Credentials in a Porter manifest can be designated build-only, such that they are not included into the resulting bundle but are available to inject into build-time config. For example:

    credentials:
      - name: repo-username
        # credential is only available at buildtime
        buildtime: true 
        default: bobby-tables
  • Build-only credentials in a Porter manifest can be interpolated (via {{ build.credentials.mybuildcred }}) in build-time config (for instance, mixin config). Note: here we use build.credentials vs bundle.credentials to distinguish build-only from bundle.

@carolynvs
Copy link
Member

Closing and tracking under #1769

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New code incoming!
Projects
None yet
Development

No branches or pull requests

2 participants