Aws-sdk-go: Missing enum value "initiatingRequest" for transit gateway peering attachment

Created on 24 Apr 2020  路  2Comments  路  Source: aws/aws-sdk-go

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

Describe the bug
When awaiting a state change on a transit gateway peering attachment, AWS returns the state initiatingRequest, but the SDK doesn't contain an enum value for this.

File : https://github.com/aws/aws-sdk-go/blob/master/service/ec2/api.go Line 112270

Version of AWS SDK for Go?
Example: v1.30.12

Version of Go (go version)?
go 1.13.5

To Reproduce (observed behavior)
Create a transit gateway peering attachment, and poll AWS API for the state, it will return initiatingRequest, rather than initiating - as is correct for a transit gateway attachment, not a peering attachment.

Noticed when working on the terraform provider code for this:
https://github.com/terraform-providers/terraform-provider-aws/pull/11162

Expected behavior
Enum should exist for this state :

TransitGatewayAttachmentStateInitiatingRequest = "initiatingRequest"

Additional context
Add any other context about the problem here.

bug service-api

Most helpful comment

Hi @j-nix, thanks for bringing this to our attention. It looks like this is a modeling issue for the service - the TransitGatewayAttachmentState member of the EC2 API model is missing the described state which is preventing this state from being populated during the code generation for our EC2 client. I've reached out to the EC2 team about this internally to have the API model include this state, once I hear back from them on this I'll update the issue accordingly.

All 2 comments

Hi @j-nix, thanks for bringing this to our attention. It looks like this is a modeling issue for the service - the TransitGatewayAttachmentState member of the EC2 API model is missing the described state which is preventing this state from being populated during the code generation for our EC2 client. I've reached out to the EC2 team about this internally to have the API model include this state, once I hear back from them on this I'll update the issue accordingly.

@diehlaws thanks for clarifying how this is generated - i'll close the PR for this and keep the issue open for your updates.

Was this page helpful?
0 / 5 - 0 ratings