You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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)The text was updated successfully, but these errors were encountered: