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

missing authorizationConfig in http datasource ? #22321

Closed
msegura opened this issue Aug 4, 2019 · 2 comments
Closed

missing authorizationConfig in http datasource ? #22321

msegura opened this issue Aug 4, 2019 · 2 comments

Comments

@msegura
Copy link

msegura commented Aug 4, 2019

Current Terraform Version

Terraform v0.12.6
+ provider.aws v2.22.0

Use-cases

A datasource of type HTTP in AppSync offers an authorizationConfig configuration object ( aws doc ).

This is useful as it allows invoking directly any aws from AppSync ( tutorial from AWS ).

It would be useful if Terraform allows creating this datasource ?

Attempted Solutions

I tried:

  http_config {
    endpoint = "https://XYZ.s3.eu-central-1.amazonaws.com"
    authorizationConfig {
      authorizationType = "AWS_IAM"
      awsIamConfig {
        signingRegion = "eu-central-1"
        signingServiceName = "s3"
      }
    }
  }

but this failed with:

Blocks of type "authorizationConfig" are not expected here.

Documentation is not mentioning anything beyond the endpoint.

Proposal

Perhaps something closely following the AWS API such as :

  http_config {
    endpoint = "https://XYZ.s3.eu-central-1.amazonaws.com"
    authorizationConfig {
      authorizationType = "AWS_IAM"
      awsIamConfig {
        signingRegion = "eu-central-1"
        signingServiceName = "s3"
      }
    }
  }

References

@ghost
Copy link

ghost commented Aug 5, 2019

This issue has been automatically migrated to hashicorp/terraform-provider-aws#9628 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-aws#9628.

@ghost
Copy link

ghost commented Sep 5, 2019

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Sep 5, 2019
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants