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
{{ message }}
This repository has been archived by the owner on Nov 5, 2024. It is now read-only.
VPC endpoint state values when parsed from their text representation are incorrect. The reason is that code expect them to be in PascalCase, while in fact they are camelCase. As a result all the values are getting classified as State::Unknown("xxx").
For example
pendingAcceptance is expected to be PendingAcceptance available is expected to be Available
etc
Expected Behavior
When running reproduction code below I expect the next output
Some(
PendingAcceptance,
),
Some(
Available
)
Current Behavior
Instead every possible VPC endpoint state in describe_vpc_endpoints() is showed as State::Unknown("text")
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugSomething isn't workingec2service-apiThis issue pertains to the AWS API
Transfered from awslabs/aws-sdk-rust: awslabs/aws-sdk-rust#619
Describe the bug
VPC endpoint state values when parsed from their text representation are incorrect. The reason is that code expect them to be in
PascalCase
, while in fact they arecamelCase
. As a result all the values are getting classified asState::Unknown("xxx")
.For example
pendingAcceptance
is expected to bePendingAcceptance
available
is expected to beAvailable
etc
Expected Behavior
When running reproduction code below I expect the next output
Current Behavior
Instead every possible VPC endpoint state in
describe_vpc_endpoints()
is showed asState::Unknown("text")
Reproduction Steps
If you have at least one VPC endpoint
Possible Solution
Additional Information/Context
No response
Version
The text was updated successfully, but these errors were encountered: