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

Request - Provide raw file to harness_platform_secret_file #774

Open
lachlan-smith opened this issue Nov 22, 2023 · 1 comment
Open

Request - Provide raw file to harness_platform_secret_file #774

lachlan-smith opened this issue Nov 22, 2023 · 1 comment

Comments

@lachlan-smith
Copy link

When using the harness_platform_secret_file resource, the provider requires the file to provided by passing in a file_path location to a local file.

This is problematic for us, as our Terraform executes using Terraform Cloud's remote execution functionality which means the local filesystem is not available at plan/execution time. Given that most files being stored will be certificates/key files, it would be helpful for the provider to allow either a path to a local file or the raw file itself.

This would allow us to for example store certificates using sensitive variables or connect to an external secret store via something like Vault and pass the raw secret directly into the Harness resource.

Our current workaround solution is to use the hashicorp/local provider and the local_sensitive_file resource to create a local file at execution time, which then can be accessed by the Harness provider. While this works, it's means that ever run will always recreate these files (so even if the Terraform plan should match the current state, a run will always be required to recreate the two files)

@mikepflu
Copy link

Has there been any movement on this? We just ran into the same problem, and I would prefer not to use the local_sensitive_file workaround.

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