-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[Bug]: data "aws_identitystore_user" not working as intended #27830
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
We have just had this happen on provider version 4.38.0 and 4.34.0 also, but not 4.33.0 and 4.32.0 (we didn't try the intermediary versions between 4.34 and 4.38 FWIW). Terraform version was 1.2.8, but it seems clear to me that it's a provider issue. |
I did try 4.34.0 and 4.37.0 (as well as 4.38.0 and 4.39.0) and got the same error. 4.33.0 was the last version that did not have this issue. For now, we've worked around this by pinning the provider but we obviously won't be able to use updates until this is fixed. |
For a little more context, here's our data source that is triggering the exception (similar to OP but not exactly the same):
|
Hi, @chris-at-covariance. I'm going to look into this. Unfortunately, the
part of the error message is what's returned by the AWS API, so we don't have any control over that |
Hi @chris-at-covariance, are you still seeing this error? I was able to recreate it last week, but not today. For some additional information:
|
I rewrote the code to work around it, it will take me a little bit to see
if it’s still a problem
We’re using us-East-1
Using Active Directory as the identity store
…-Chris
On Mon, Dec 5, 2022 at 15:41 Graham Davison ***@***.***> wrote:
Hi @chris-at-covariance <https://github.com/chris-at-covariance>, are you
still seeing this error? I was able to recreate it last week, but not today.
For some additional information:
1.
What region are you using?
2.
Which type of Identity Source are you using to back your Identity
Store: Identity Center directory, Active Directory, or an External Identity
Provider?
—
Reply to this email directly, view it on GitHub
<#27830 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A32CNR25MN4CCZR563OHF43WLZHOZANCNFSM6AAAAAASBPR2DY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
This message is intended only for the use of the Addressee and may contain
information that is privileged and confidential. If you are not the
intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this
communication in error, please erase all copies of the message and its
attachments and notify us immediately.
|
I did some digging around after encountering the same issue but for the aws_identitystore_group which had the very same change in its behaviour. Posting here, as the underlying issue is the same. I did my debugging with the groups data object, but this should not be a difference to the user one. AWS Region: eu-central-1 Everything works with the terraform-provider-aws in version <= 3.40 with the following configuration:
After upgrading the provider and adjusting the deprecated filtering as follows, it does not work anymore:
Looking at the requests in debug mode, one can see that the request using the new Previous Versions:
|
@chris-at-covariance We were unable to reproduce this in our acceptance tests, so I went ahead and restored the old |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
1.3.4
AWS Provider Version
4.39.0
Affected Resource(s)
according to the docs for data aws_identitystore_user. I should be able to retrieve a user from the identity store. provider using code that looks like this:
Expected Behavior
data.aws_identitystore_user.lee_user.id
should be assigned the value of the user with the UserName "lee@example.com"if an error occurs, it should appropriately identify that error
Actual Behavior
api error UnknownOperationException: UnknownError was raised
Relevant Error/Panic Output Snippet
Terraform Configuration Files
see above
Steps to Reproduce
see above
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
No response
The text was updated successfully, but these errors were encountered: