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

Enum values for VpcEndpoint.State doesn't match the values that DescribeVpcEndpoints returns #2864

Open
3 tasks done
wjam opened this issue Sep 23, 2020 · 9 comments
Open
3 tasks done
Assignees
Labels
bug This issue is a bug. service-api This issue is due to a problem in a service API, not the SDK implementation.

Comments

@wjam
Copy link

wjam commented Sep 23, 2020

Confirm by changing [ ] to [x] below to ensure that it's a bug:

Describe the bug
The enum values for the State field in ec2.VpcEndpoint (StatePendingAcceptance, StatePending, StateAvailable, StateDeleting, StateRejected, StateFailed & StateExpired) don't match the actual values returned when performing DescribeVpcEndpoints. The returned value has the first character is always lower case but the enum values in this SDK has them as uppercase.

Version of AWS SDK for Go?
v1.27.1, although the problem still exists in master

Version of Go (go version)?
N/A

To Reproduce (observed behavior)
Perform ec2:DescribeVpcEndpoints and observe the values of the State attribute returned in the response. See if those values match the enum values in State...

Expected behavior
The State... enum values should match what is returned by DescribeVpcEndpoints, just like the InstanceLifecycleType enum matches the value returned for the InstanceLifecycle attribute in the ec2:DescribeInstances

Additional context

@KaibaLopez
Copy link
Contributor

Hi, Sorry for the lack of response here, you are right I can reproduce this inconsistency.

@skmcgrail
Copy link
Member

skmcgrail commented Aug 26, 2021

This is an issue with the service not correctly modeling and using the enum values they have modeled. This is evident in a captured wire dump of the response. Transferring to aws-sdk repository for further follow-up.

@skmcgrail skmcgrail transferred this issue from aws/aws-sdk-go Aug 26, 2021
@KaibaLopez KaibaLopez self-assigned this Sep 27, 2021
@vudh1 vudh1 assigned vudh1 and unassigned KaibaLopez Mar 14, 2022
@vudh1 vudh1 added the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Mar 15, 2022
@github-actions
Copy link

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

@github-actions github-actions bot added the closing-soon This issue will automatically close in 4 days unless further comments are made. label Aug 11, 2022
@wjam
Copy link
Author

wjam commented Aug 11, 2022

This has still not yet been addressed

@github-actions github-actions bot removed closing-soon This issue will automatically close in 4 days unless further comments are made. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. labels Aug 12, 2022
@vudh1
Copy link
Contributor

vudh1 commented Aug 19, 2022

P70319347

@RanVaknin RanVaknin added bug This issue is a bug. service-api This issue is due to a problem in a service API, not the SDK implementation. labels Sep 6, 2022
@vudh1 vudh1 assigned RanVaknin and unassigned vudh1 Sep 9, 2022
@RanVaknin RanVaknin assigned yasminetalby and unassigned RanVaknin Sep 25, 2023
@ashishdhingra
Copy link

Contacted service team requesting for an update. Awaiting response.

@ashishdhingra
Copy link

Pinged service team again for update. Awaiting response.

@ashishdhingra
Copy link

Contacted service team requesting for an update. Awaiting response.

1 similar comment
@ashishdhingra
Copy link

Contacted service team requesting for an update. Awaiting response.

@bhavya2109sharma bhavya2109sharma transferred this issue from aws/aws-sdk Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. service-api This issue is due to a problem in a service API, not the SDK implementation.
Projects
None yet
Development

No branches or pull requests

8 participants