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

[FEATURE]: Support Environment Variables in Dell OME Provider Block #126

Open
dprillxyz opened this issue Nov 25, 2024 · 0 comments
Open

Comments

@dprillxyz
Copy link

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
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

1 participant