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
For now, the sn terraform provider only supports key_file_path as the provider auth, but for some secture scenarios using the file path means users need to store the file in some places and may have leak risks. So, ideally should support the provider auth with string parametres and support the env parameters to pass.
Solution
We can support sn provider auth with client_id and client_secret.
Hi @ericsyh Even after removing the key_file_path from both the provider block and the variable file, when I execute the terraform plan command, it continues to prompt for the key_file_path. Subsequently, when I provide the name of a dummy file, an error occurs indicating that the file's code is incorrect.
Even after removing the key_file_path from both the provider block and the variable file, when I execute the terraform plan command, it continues to prompt for the key_file_path. Subsequently, when I provide the name of a dummy file, an error occurs indicating that the file's code is incorrect.
@saurabh31090 this is a feature plan to implement but not yet supported.
Background
For now, the sn terraform provider only supports
key_file_path
as the provider auth, but for some secture scenarios using the file path means users need to store the file in some places and may have leak risks. So, ideally should support the provider auth with string parametres and support the env parameters to pass.Solution
We can support sn provider auth with
client_id
andclient_secret
.Usage with provider parameters
Usage with env parameters
The text was updated successfully, but these errors were encountered: