Open bashfulrobot opened 1 month ago
While you wait for a fix, you can require the previous release which will probably fix this:
` terraform { required_providers { libvirt = { source = "dmacvicar/libvirt"
}
} }
`
This is occuring here, which I guess has to be amended to be more like this.
Would like to point out that this issue was very likely silently failing previously if it was working at all. This code path was never tilde (~) aware. fyi @johnbent @bashfulrobot @dmacvicar
Edit: I am opening a new PR and will outline these things there.
System Information
Linux distribution
Terraform version
Provider and libvirt versions
Checklist
No
[x] 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.
My assumption is that if others were using an SSH connection and ran into this issue, they would want to know the default/expected behaviours.
[X] If it is a very special case, consider using the XSLT support in the provider to tweak the definition instead of opening an issue
I feel like this warrants an issue, as to be it is not a special case.
[X] Maintainers do not have expertise in every libvirt setting, so please, describe the feature and how it is used. Link to the appropriate documentation
docs detailing supported extra parameters on the URI for libvirt.
Description of Issue/Question
Setup
variables.tf
provider.tf
extensions.tf
main.tf
network.tf
volumes.tf
controlplane.tf
worker.tf
Steps to Reproduce Issue
terraform init
terraform plan
Error
If I then change my connection string to
uri = "qemu+ssh://dustin@192.168.168.1/system?knownhosts=/home/dustin/.ssh/known_hosts"
it will work. I also tested withuri = "qemu+ssh://dustin@192.168.168.1/system?knownhosts=~/.ssh/known_hosts"
which also failed. It seems like it no longer understands~
.Additional information:
Do you have SELinux or Apparmor/Firewall enabled? Some special configuration?
Have you tried to reproduce the issue without them enabled?
I noted that the SSH Config stuff was reworked for
0.8.0
. Is this behaviour intended?Thank you in advance.