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

Use endpoint from keystone in cinder client #16

Merged
merged 1 commit into from Nov 13, 2015

Conversation

bz2
Copy link
Contributor

@bz2 bz2 commented Nov 4, 2015

Fixes LP:1512399, "Get https:... local error: record overflow".

Previously the autogenerated code was inventing URLs to match a
particular form, then updating just the host to match the real
endpoint. This is insufficient if either the scheme is not https
or if there are other leading path components.

The autogenerated client code has already been manually edited,
this change drops the pretense we can regenerate it, the master
copy of the WADL files no longer works.

There are some minor api changes here, the signature of NewClient
has been changed, but the Basic entry point used by the openstack
provider in juju is untouched. Also, the use of v2 paths is no
longer enforced by the code through simply ignoring the keystone
return values. Callers must verify the endpoint they are using
is v2 if they require v2 functionality.

Fixes LP:1512399, "Get https:... local error: record overflow".

Previously the autogenerated code was inventing URLs to match a
particular form, then updating just the host to match the real
endpoint. This is insufficient if either the scheme is not https
or if there are other leading path components.

The autogenerated client code has already been manually edited,
this change drops the pretense we can regenerate it, the master
copy of the WADL files no longer works.

There are some minor api changes here, the signature of NewClient
has been changed, but the Basic entry point used by the openstack
provider in juju is untouched. Also, the use of v2 paths is no
longer enforced by the code through simply ignoring the keystone
return values. Callers must verify the endpoint they are using
is v2 if they require v2 functionality.
// This file is not intended to be updated by hand, rather it should
// be regenerated every time this library is built. The WADLs were
// originally sourced from:
// This file was initially autogenerated from the upstream wadl file, but has
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes me sad, but the WADL format really isn't complete enough to auto-generate everything anyway. Pity.

@axw
Copy link
Member

axw commented Nov 5, 2015

LGTM

@bz2
Copy link
Contributor Author

bz2 commented Nov 13, 2015

$$merge$$

@jujubot
Copy link
Member

jujubot commented Nov 13, 2015

Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-goose

jujubot added a commit that referenced this pull request Nov 13, 2015
Use endpoint from keystone in cinder client

Fixes LP:1512399, "Get https:... local error: record overflow".

Previously the autogenerated code was inventing URLs to match a
particular form, then updating just the host to match the real
endpoint. This is insufficient if either the scheme is not https
or if there are other leading path components.

The autogenerated client code has already been manually edited,
this change drops the pretense we can regenerate it, the master
copy of the WADL files no longer works.

There are some minor api changes here, the signature of NewClient
has been changed, but the Basic entry point used by the openstack
provider in juju is untouched. Also, the use of v2 paths is no
longer enforced by the code through simply ignoring the keystone
return values. Callers must verify the endpoint they are using
is v2 if they require v2 functionality.
@jujubot jujubot merged commit e4a91e8 into go-goose:v1 Nov 13, 2015
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

Successfully merging this pull request may close these issues.

None yet

3 participants