-
Notifications
You must be signed in to change notification settings - Fork 115
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
Support communicating with Xen API over https #85
Comments
chqr
changed the title
Optional config flag remote_url to support communicating with Xen API over https
Support communicating with Xen API over https
Jun 30, 2017
chqr
pushed a commit
to chqr/packer-builder-xenserver
that referenced
this issue
Jul 5, 2017
chqr
pushed a commit
to chqr/packer-builder-xenserver
that referenced
this issue
Jul 5, 2017
chqr
pushed a commit
to chqr/packer-builder-xenserver
that referenced
this issue
Jul 5, 2017
chqr
pushed a commit
to chqr/packer-builder-xenserver
that referenced
this issue
Jul 5, 2017
chqr
pushed a commit
to chqr/packer-builder-xenserver
that referenced
this issue
Jul 5, 2017
chqr
pushed a commit
to chqr/packer-builder-xenserver
that referenced
this issue
Jul 5, 2017
NeilHanlon
pushed a commit
to kayak/packer-builder-xenserver
that referenced
this issue
Aug 15, 2019
NeilHanlon
pushed a commit
to kayak/packer-builder-xenserver
that referenced
this issue
Aug 15, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For security reasons, we'd like to avoid transmitting XenServer credentials in the clear. It looks like under the hood this project is using the Go standard library's http implementation, which supports https.
Are there any objections to adding a
remote_url
config flag, so that users can specify http/https according to their needs? It looks like the value ofremote_url
could simply be passed in to XenAPIClient, and could default to "http://${remote_host}" (the current behavior).The text was updated successfully, but these errors were encountered: