-
Notifications
You must be signed in to change notification settings - Fork 61
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
Default service URLs has to be consistent accross all IAM SDKs #166
Comments
Hi @kavya498, this change would need to be done by the service team that owns the IAM Access Groups API. First the API definition would need to change (the "/v2" part would need to be moved from the server url definition to each of the path entries within the API definition), then the SDK code for each of the SDKs will need to be re-generated and delivered in a new release of each SDK. |
@mamillapalle Nagarjuna, could you please take this one? |
@padamstx I will take care of this. |
@narinder-kaur Just added you to the "writers" group for the platform services SDK projects. This should allow you to push a new branch and open a PR without having to use a fork. |
The platform-services SDKs have all been updated to reflect the updated API definition where the "/v2" part of the service URL was moved to each individual path value. This will now allow a user to use a service URL like |
IAM Identity and IAMPAP uses default service url as
iam.cloud.ibm.com
where as IAM Access group uses
iam.cloud.ibm.com/v2
Terraform Provider uses one common environment variable
IBMCLOUD_IAM_API_ENDPOINT
for IAM related resources..Since SDK is not consistent this would break provider when IBMCLOUD_IAM_API_ENDPOINT environment variable is exported..
Request to make default url as
iam.cloud.ibm.com
for IAM access group as well..Thanks
The text was updated successfully, but these errors were encountered: