r/aws_appmesh_route: Add support for HTTP-header-based routing and route priorities

[ewbankkit]

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" comments, they generate extra noise for pull request followers and do not help prioritize the request

Closes #9802.

Release note for CHANGELOG:

resource/aws_appmesh_route: Add `priority` and `header` attributes to support route priorities and HTTP-header-based routing

Output from acceptance testing:

$ make testacc TEST=./aws TESTARGS='-run=TestAccAWSAppmesh/Route/'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -parallel 20 -run=TestAccAWSAppmesh/Route/ -timeout 120m
=== RUN   TestAccAWSAppmesh
=== RUN   TestAccAWSAppmesh/Route
=== RUN   TestAccAWSAppmesh/Route/tcpRoute
=== RUN   TestAccAWSAppmesh/Route/routePriority
=== RUN   TestAccAWSAppmesh/Route/tags
=== RUN   TestAccAWSAppmesh/Route/httpHeader
=== RUN   TestAccAWSAppmesh/Route/httpRoute
=== RUN   TestAccAWSAppmesh/VirtualRouter
=== RUN   TestAccAWSAppmesh/VirtualRouter/basic
=== RUN   TestAccAWSAppmesh/VirtualRouter/tags
--- PASS: TestAccAWSAppmesh (289.67s)
    --- PASS: TestAccAWSAppmesh/Route (206.69s)
        --- PASS: TestAccAWSAppmesh/Route/tcpRoute (41.59s)
        --- PASS: TestAccAWSAppmesh/Route/routePriority (40.44s)
        --- PASS: TestAccAWSAppmesh/Route/tags (42.81s)
        --- PASS: TestAccAWSAppmesh/Route/httpHeader (41.00s)
        --- PASS: TestAccAWSAppmesh/Route/httpRoute (40.84s)
    --- PASS: TestAccAWSAppmesh/VirtualRouter (82.98s)
        --- PASS: TestAccAWSAppmesh/VirtualRouter/basic (34.33s)
        --- PASS: TestAccAWSAppmesh/VirtualRouter/tags (48.65s)
PASS
ok  	github.com/terraform-providers/terraform-provider-aws/aws	289.741s

[ewbankkit]

• Includes commit from Update module aws/aws-sdk-go to v1.23.12 #9770 to upgrade AWS SDK version
• Relevant commits cherry picked from [WIP] App Mesh preview - HTTP header based routing, route priorities, cookie based routing and retry policy #9468
• Using hard-coded HTTP method names rather that SDK provided constants until App Mesh API Go SDK HttpMethod enum values incorrect casing aws/aws-app-mesh-roadmap#93 is addressed

[ewbankkit]

The SDK-provided constants can now be used.
Requires:

• Update module aws/aws-sdk-go to v1.23.12 #9770

[ewbankkit]

Pulled in latest AWS SDK and reverted to using the SDK-defined constants.
Re-ran acceptance tests:

$ make testacc TEST=./aws TESTARGS='-run=TestAccAWSAppmesh/Route/'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -parallel 20 -run=TestAccAWSAppmesh/Route/ -timeout 120m
=== RUN   TestAccAWSAppmesh
=== RUN   TestAccAWSAppmesh/Route
=== RUN   TestAccAWSAppmesh/Route/httpRoute
=== RUN   TestAccAWSAppmesh/Route/tcpRoute
=== RUN   TestAccAWSAppmesh/Route/routePriority
=== RUN   TestAccAWSAppmesh/Route/tags
=== RUN   TestAccAWSAppmesh/Route/httpHeader
=== RUN   TestAccAWSAppmesh/VirtualRouter
=== RUN   TestAccAWSAppmesh/VirtualRouter/basic
=== RUN   TestAccAWSAppmesh/VirtualRouter/tags
--- PASS: TestAccAWSAppmesh (287.46s)
    --- PASS: TestAccAWSAppmesh/Route (203.56s)
        --- PASS: TestAccAWSAppmesh/Route/httpRoute (41.38s)
        --- PASS: TestAccAWSAppmesh/Route/tcpRoute (40.65s)
        --- PASS: TestAccAWSAppmesh/Route/routePriority (40.69s)
        --- PASS: TestAccAWSAppmesh/Route/tags (40.99s)
        --- PASS: TestAccAWSAppmesh/Route/httpHeader (39.85s)
    --- PASS: TestAccAWSAppmesh/VirtualRouter (83.90s)
        --- PASS: TestAccAWSAppmesh/VirtualRouter/basic (34.80s)
        --- PASS: TestAccAWSAppmesh/VirtualRouter/tags (49.10s)
PASS
ok  	github.com/terraform-providers/terraform-provider-aws/aws	287.530s

[ewbankkit]

Closing in favor of #9964.
Easier to create a new PR than deal with git rebase conflicts.

[ghost]

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.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!