vSphere provider - add support for custom configuration fields #3834
Labels
Comments
|
It is done ... |
omeid
pushed a commit
to omeid/terraform
that referenced
this issue
Mar 30, 2018
…sis_firehose_delivery_stream-arn-import-crash resource/aws_kinesis_firehose_delivery_stream: Prevent crash on malformed ID for import
omeid
pushed a commit
to omeid/terraform
that referenced
this issue
Mar 30, 2018
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am working on this feature currently. This allows tagging a virtual machine with metadata. This is a feature that mantl.io requires. Will submit a pull request.
Adding custom_configurations map variable. Then read write crud in the vSphere provider. This data will be stored within vSphere's extra config capability.
The text was updated successfully, but these errors were encountered: