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

feat(IAM Identity): adding userExpm list and token lifetime #221

Merged
merged 1 commit into from
Nov 23, 2022

Conversation

pooraniss-ibm
Copy link
Member

@pooraniss-ibm pooraniss-ibm commented Nov 22, 2022

Signed-off-by: poorani poorani.senthilkumar.sankari@ibm.com

PR summary

Adding user exception list and token lifetime to IAM account settings

PR Checklist

Please make sure that your PR fulfills the following requirements:

  • The commit message follows the Angular Commit Message Guidelines.
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

Current vs new behavior

Adding user exception list and token lifetime to IAM account settings

Does this PR introduce a breaking change?

  • Yes
  • No

Copy link
Member

@padamstx padamstx left a comment

Choose a reason for hiding this comment

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

Changes look good, except for my comment re: the account_id -> account-id change. I didn't notice that when I reviewed the java PR :)

}

builder := core.NewRequestBuilder(core.POST)
builder = builder.WithContext(ctx)
builder.EnableGzipCompression = iamIdentity.GetEnableGzipCompression()
_, err = builder.ResolveRequestURL(iamIdentity.Service.Options.URL, `/v1/activity/accounts/{account_id}/report`, pathParamsMap)
_, err = builder.ResolveRequestURL(iamIdentity.Service.Options.URL, `/v1/activity/accounts/{account-id}/report`, pathParamsMap)
Copy link
Member

Choose a reason for hiding this comment

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

looks like this path param was changed from using snake-case (which is correct) to using kebab case (which is incorrect). Why the change? Did you run the openapi-validator on the updated API definition???

Copy link
Member Author

Choose a reason for hiding this comment

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

oh yes, I did generate using the latest API definition, was wondering which could be correct. I will change it back to snake_case.

Copy link
Member Author

Choose a reason for hiding this comment

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

@padamstx updated :)

Signed-off-by: poorani <poorani.senthilkumar.sankari@ibm.com>
@pooraniss-ibm pooraniss-ibm force-pushed the iam-identity-account-settings branch from a72dea0 to 90f4b8d Compare November 23, 2022 10:58
@pooraniss-ibm pooraniss-ibm added the enhancement New feature or request label Nov 23, 2022
@padamstx padamstx merged commit c9d55a8 into main Nov 23, 2022
@padamstx padamstx deleted the iam-identity-account-settings branch November 23, 2022 15:14
ibm-devx-sdk pushed a commit that referenced this pull request Nov 23, 2022
# [0.31.0](v0.30.0...v0.31.0) (2022-11-23)

### Features

* **IAM Identity:** adding userExpm list and token lifetime ([#221](#221)) ([c9d55a8](c9d55a8))
@ibm-devx-sdk
Copy link

🎉 This PR is included in version 0.31.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

adya1303 pushed a commit that referenced this pull request Dec 6, 2022
Signed-off-by: poorani <poorani.senthilkumar.sankari@ibm.com>
Signed-off-by: ADYA NAND JHA <ADYA.NAND.Jha1@ibm.com>
adya1303 pushed a commit that referenced this pull request Dec 6, 2022
# [0.31.0](v0.30.0...v0.31.0) (2022-11-23)

### Features

* **IAM Identity:** adding userExpm list and token lifetime ([#221](#221)) ([c9d55a8](c9d55a8))

Signed-off-by: ADYA NAND JHA <ADYA.NAND.Jha1@ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants