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
Is your issue/contribution related with enabling some setting/option exposed by libvirt that the plugin does not yet support, or requires changing/extending the provider terraform schema?
Make sure you explain why this option is important to you, why it should be important to everyone. Describe your use-case with detail and provide examples where possible.
If it is a very special case, consider using the XSLT support in the provider to tweak the definition instead of opening an issue
Maintainers do not have expertise in every libvirt setting, so please, describe the feature and how it is used. Link to the appropriate documentation
Is it a bug or something that does not work as expected? Please make sure you fill the version information below:
Description of Issue/Question
Setup
I have a very plain terraform setup, coming from the 0.6.x days. The domain definition looks like this
System Information
Linux distribution
openSUSE Tumbleweed
Terraform version
Provider and libvirt versions
Checklist
Is your issue/contribution related with enabling some setting/option exposed by libvirt that the plugin does not yet support, or requires changing/extending the provider terraform schema?
Is it a bug or something that does not work as expected? Please make sure you fill the version information below:
Description of Issue/Question
Setup
I have a very plain terraform setup, coming from the 0.6.x days. The domain definition looks like this
I upgraded from 0.6.14 to 0.7.6 and
terraform plan
now wants to recreate my domains, e.g.I checked the VM definitions via virt-manager and they all start with
Steps to Reproduce Issue
I guess start with 0.6.x and upgrade to 0.7.x?
Additional information:
Do you have SELinux or Apparmor/Firewall enabled? Some special configuration?
No.
Have you tried to reproduce the issue without them enabled?
N/A
This behaviour seems to have been brought in via #1045
The text was updated successfully, but these errors were encountered: