Skip to content
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.

Allow Runner Git configuration to access environment/dynamic values #3921

Open
arbourd opened this issue Sep 22, 2022 · 1 comment
Open

Allow Runner Git configuration to access environment/dynamic values #3921

arbourd opened this issue Sep 22, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@arbourd
Copy link

arbourd commented Sep 22, 2022

Is your feature request related to a problem? Please describe.

I'd rather configure git data sources and their keys with either an environmental variable or with the the dynamic function. Having to call a script that does waypoint project apply -git-private-key-path="" is less fun.

Describe the solution you'd like

Here is an example of using the dynamic block to pull the private key from the Kubernetes secret.

runner {
  enabled = true

  data_source "git" {
    url  = "git@github.com:example/repo.git"
    path = "waypoint"
    key = dynamic("kubernetes", {
      name   = "git"
      key    = "identity"
      secret = true
    })
  }
}

Describe alternatives you've considered

I use the command line.

Explain any additional use-cases

For GitOps, I want everything configured in a file. Right now we're using a CronJob in Kubernetes to update projects/keys. Not so sexy.

@arbourd arbourd added the new label Sep 22, 2022
@paladin-devops
Copy link
Contributor

Hey @arbourd! The data source is used when the project is first "init-ed", not continuously through the lifecycle of the project. We will look into ways to retrieve the value here earlier in the project operations!

@paladin-devops paladin-devops added enhancement New feature or request and removed new labels Sep 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants