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
Describe the solution you'd like
It would be beneficial to allow the use of environment variables in the provider block. This would make it easier to manage sensitive information such as passwords by allowing users to configure the provider settings via environment variables instead of hardcoding them into the configuration files.
// for example
export OME_USERNAME=""
export OME_PASSWORD=""
export OME_HOST=""
Describe alternatives you've considered
Currently, users must manually input their credentials and other provider-specific values directly into the Terraform provider block, which can expose sensitive information in source control or configuration files. Using environment variables would improve security and flexibility.
As an alternative, one could use Terraform variable blocks combined with .tfvars files to manage configuration, but environment variables offer a more secure and dynamic approach for managing secrets without needing extra files.
Additional context
Providing support for environment variables in the Dell OME Terraform provider aligns with best practices in Terraform configuration management, particularly for users who work in CI/CD pipelines or need to manage different environments (e.g., production, staging) securely. This is a common pattern supported by other Terraform providers (e.g., AWS, Azure), and adding similar functionality to the Dell OME provider would enhance its usability and security.
Community Note
Please vote on this issue by adding a 👍 reaction
to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions,
they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
It would be beneficial to allow the use of environment variables in the provider block. This would make it easier to manage sensitive information such as passwords by allowing users to configure the provider settings via environment variables instead of hardcoding them into the configuration files.
Describe alternatives you've considered
Currently, users must manually input their credentials and other provider-specific values directly into the Terraform provider block, which can expose sensitive information in source control or configuration files. Using environment variables would improve security and flexibility.
As an alternative, one could use Terraform variable blocks combined with .tfvars files to manage configuration, but environment variables offer a more secure and dynamic approach for managing secrets without needing extra files.
Additional context
Providing support for environment variables in the Dell OME Terraform provider aligns with best practices in Terraform configuration management, particularly for users who work in CI/CD pipelines or need to manage different environments (e.g., production, staging) securely. This is a common pattern supported by other Terraform providers (e.g., AWS, Azure), and adding similar functionality to the Dell OME provider would enhance its usability and security.
Community Note
to the original issue to help the community and maintainers prioritize this request
they generate extra noise for issue followers and do not help prioritize the request
The text was updated successfully, but these errors were encountered: