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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Terraform CLI and Terraform IBM Provider Version
Terraform v1.1.5
on linux_amd64
Affected Resource(s)
iam_access_group data source
Expected Behavior
The iam_access_group data source should be able to see all resource groups that exist within an account.
Actual Behavior
The iam_access_group can't see more than the first 50 access groups within an account. I suspect that the terrafor provider is not using paged results of the IAM API, and is only looking at the first page with a limit of 50. If your account has more than 50 access groups, only those that fall within the first page are recognized by the data source.
You get a runtime error like this:
╷
│ Error: [ERROR] No Access Groups with name ZOS_DEV_VIEW in Account
│
│ with module.ibm-access-group.data.ibm_iam_access_group.viewers,
│ on .terraform/modules/ibm-access-group/main.tf line 71, in data "ibm_iam_access_group" "viewers":
│ 71: data ibm_iam_access_group viewers {
│
Even though the access group does, in fact, exist within the account:
Steps to Reproduce
Have an account with more than 50 access groups
Try to read an access group that isn't within the first 50:
data "ibm_iam_access_group" "accgroup" {
access_group_name = ZOS_DEV_VIEW
}
The text was updated successfully, but these errors were encountered:
Community Note
Terraform CLI and Terraform IBM Provider Version
Affected Resource(s)
iam_access_group
data sourceExpected Behavior
The
iam_access_group
data source should be able to see all resource groups that exist within an account.Actual Behavior
The
iam_access_group
can't see more than the first 50 access groups within an account. I suspect that the terrafor provider is not using paged results of the IAM API, and is only looking at the first page with a limit of 50. If your account has more than 50 access groups, only those that fall within the first page are recognized by the data source.You get a runtime error like this:
Even though the access group does, in fact, exist within the account:
Steps to Reproduce
The text was updated successfully, but these errors were encountered: