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
It appears in commit db0ae14 the option to provide Rackspace API keys (an extension to the keystone API) was removed. Packer currently provides an option for passing the API key.
I can't see any sign of the API keys for Rackspace being deprecated, so will RAX-KSKEY be added back into gophercloud? What is the status of support for Rackspace being driven by gophercloud?
Thanks!
The text was updated successfully, but these errors were encountered:
Rackspace-specific code won't be added to this repository.
What is the status of support for Rackspace being driven by gophercloud?
Gophercloud has shifted focus to exclusively support OpenStack proper. You should be able to use it with Rackspace Private Cloud but probably not Rackspace Public Cloud. For Rackspace Public Cloud, you can continue to use the rackspace/gophercloud repo.
* Identity v3: Token Data Source
This commit adds the `openstack_identity_token_v3` data source.
It can be used to obtain authentication information about the
current token in use. This can be used as self-discovery or
introspection of the username or project name currently in use.
* Identity v3: Rename openstack_identity_token_v3 to openstack_identity_auth_scope_v3
It appears in commit db0ae14 the option to provide Rackspace API keys (an extension to the keystone API) was removed. Packer currently provides an option for passing the API key.
I can't see any sign of the API keys for Rackspace being deprecated, so will RAX-KSKEY be added back into gophercloud? What is the status of support for Rackspace being driven by gophercloud?
Thanks!
The text was updated successfully, but these errors were encountered: