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

Allow ClientSecret as EnvironmentVariable #44

Open
mdepedrof opened this issue Jul 9, 2024 · 3 comments
Open

Allow ClientSecret as EnvironmentVariable #44

mdepedrof opened this issue Jul 9, 2024 · 3 comments

Comments

@mdepedrof
Copy link

For Security reasons its a good practise not hardcoded Secrets on your code. If you puts your code on a repository you are publishing your clientSecret for your Infisical environment.

The recomendation, like other providers, is allow to set the provider configs using envorinments variables.

Thanks!

@WladyX
Copy link

WladyX commented Sep 29, 2024

I came searching for the same thing, also need this, @maidul98 is this something you're looking into?
Thank you for infisical & for this provider!

@WladyX
Copy link

WladyX commented Sep 29, 2024

in the mean time you can workaround like this:

provider "infisical" {
  host          = "https://infisical.example.com"
  client_id     = var.infisical_client_id
  client_secret = var.infisical_client_secret
}

variable "infisical_client_id" {
  type    = string
  default = ""
  # sensitive = true
}

variable "infisical_client_secret" {
  type    = string
  default = ""
  # sensitive = true
}

and export the vars like TF_VAR_infisical_client_secret=... and TF_VAR_infisical_client_id=...

@mdepedrof
Copy link
Author

yes, this is the way i have setting up but this is not the most secure way.

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

No branches or pull requests

2 participants