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
I think it would be helpful to add the token to the env var HCLOUD_TOKEN if not already present.
This would help when using external scripts (e.g. terraform_data resource with local provisioner) that require a Hetzner Cloud API Token.
My usecase: I am checking if a hcloud snapshot exists (using the hcloud_images data source), if not I am calling the hcloud-upload-image binary using a terraform_data resource. So it would be helpful to use the same token as the provider and therefor the token must/should be exported as HCLOUD_TOKEN.
What whould you like to see?
I think it would be helpful to add the token to the env var
HCLOUD_TOKEN
if not already present.This would help when using external scripts (e.g.
terraform_data
resource with local provisioner) that require a Hetzner Cloud API Token.My usecase: I am checking if a hcloud snapshot exists (using the
hcloud_images
data source), if not I am calling the hcloud-upload-image binary using aterraform_data
resource. So it would be helpful to use the same token as the provider and therefor the token must/should be exported asHCLOUD_TOKEN
.See example
add_address_to_env
from terraform-provider-vaultThe text was updated successfully, but these errors were encountered: