Add HTTP datasource authorization_config fields.

[maddijoyce]

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" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Closes #12721 #9628

Release note for CHANGELOG:

resource/aws_appsync_graphql_api: Add `authorization_config` block to `http_config`

Output from acceptance testing:

$ make testacc TEST=./aws TESTARGS='-run=TestAccAwsAppsyncDatasource_HTTPConfig'

==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -count 1 -parallel 20 -run=TestAccAwsAppsyncDatasource_HTTPConfig -timeout 120m
=== RUN   TestAccAwsAppsyncDatasource_HTTPConfig_AuthorizationConfig
=== PAUSE TestAccAwsAppsyncDatasource_HTTPConfig_AuthorizationConfig
=== RUN   TestAccAwsAppsyncDatasource_HTTPConfig_Endpoint
=== PAUSE TestAccAwsAppsyncDatasource_HTTPConfig_Endpoint
=== CONT  TestAccAwsAppsyncDatasource_HTTPConfig_AuthorizationConfig
=== CONT  TestAccAwsAppsyncDatasource_HTTPConfig_Endpoint
--- PASS: TestAccAwsAppsyncDatasource_HTTPConfig_AuthorizationConfig (45.24s)
--- PASS: TestAccAwsAppsyncDatasource_HTTPConfig_Endpoint (65.48s)
PASS
ok  	github.com/terraform-providers/terraform-provider-aws/aws	66.791s

[Callumccr]

This is definitely needed!

[maddijoyce]

@bflad Sorry if you're the wrong person to ping on this, but I'm wondering what the chances of this getting into the aws provider are?

[ignaciopeixoto]

Is this stuck just because some linting failed?

[zhelding]

Pull request #21306 has significantly refactored the AWS Provider codebase. As a result, most PRs opened prior to the refactor now have merge conflicts that must be resolved before proceeding.

Specifically, PR #21306 relocated the code for all AWS resources and data sources from a single aws directory to a large number of separate directories in internal/service, each corresponding to a particular AWS service. This separation of code has also allowed for us to simplify the names of underlying functions -- while still avoiding namespace collisions.

We recognize that many pull requests have been open for some time without yet being addressed by our maintainers. Therefore, we want to make it clear that resolving these conflicts in no way affects the prioritization of a particular pull request. Once a pull request has been prioritized for review, the necessary changes will be made by a maintainer -- either directly or in collaboration with the pull request author.

For a more complete description of this refactor, including examples of how old filepaths and function names correspond to their new counterparts: please refer to issue #20000.

For a quick guide on how to amend your pull request to resolve the merge conflicts resulting from this refactor and bring it in line with our new code patterns: please refer to our Service Package Refactor Pull Request Guide.

[ewbankkit]

Superseded by #22411.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.