We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://developer.rackspace.com/docs/cloud-networks/v2/api-reference/shared-ip-address-operations/#explicitly-associate-ip-address-with-server https://developer.rackspace.com/docs/cloud-networks/v2/api-reference/shared-ip-address-operations/#show-specific-ip-addresses-explicitly-associated-with-server https://developer.rackspace.com/docs/cloud-networks/v2/api-reference/shared-ip-address-operations/#delete-association-between-ip-address-and-server
All example URLs need to be updated with tenant in the correct path in the URL: /v2/{tenantID}/servers/{serverID}/ip_associations/{IPAddressID}
/v2/{tenantID}/servers/{serverID}/ip_associations/{IPAddressID}
Currently they lack tenant in the proper place for the path, so the call will likely return a 401 since it's treating the server id as the tenant id.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
https://developer.rackspace.com/docs/cloud-networks/v2/api-reference/shared-ip-address-operations/#explicitly-associate-ip-address-with-server
https://developer.rackspace.com/docs/cloud-networks/v2/api-reference/shared-ip-address-operations/#show-specific-ip-addresses-explicitly-associated-with-server
https://developer.rackspace.com/docs/cloud-networks/v2/api-reference/shared-ip-address-operations/#delete-association-between-ip-address-and-server
All example URLs need to be updated with tenant in the correct path in the URL:
/v2/{tenantID}/servers/{serverID}/ip_associations/{IPAddressID}Currently they lack tenant in the proper place for the path, so the call will likely return a 401 since it's treating the server id as the tenant id.
The text was updated successfully, but these errors were encountered: