-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
fix(appsync): HttpDataSource extends BackedDataSource instead of BaseDataSource #11185
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MrArnoldPalmer this LGTM, maybe a test case is needed but other than that im good with it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 LGTM. TY!
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
…DataSourceProps` (#32065) ### Reason for this change Closes #31979. Replaces #29689. In #11185, the `HttpDataSource` class was updated to extend `BackedDataSource` instead of `BaseDataSource`, however the `HttpDataSourceProps` type wasn't updated to reflect this change. This PR makes the `HttpDataSourceProps` type reflect the change. ### Description of changes Makes the `HttpDataSourceProps` type extend `BackedDataSourceProps`, instead of `BaseDataSourceProps`. This means users are able to provide the `serviceRole` prop without getting a type error. ### Description of how you validated changes The below code snippet no longer gives an incorrect type error when providing the serviceRole, as it did before: ```ts import * as appsync from "aws-cdk-lib/aws-appsync"; import type { IRole } from "aws-cdk-lib/aws-iam"; declare const myApi: appsync.GraphqlApi; declare const serviceRole: IRole; const stepFunctionHttpDataSource = new appsync.HttpDataSource( myApi, "MyStepFunctionHTTPDataSource", { api: myApi, authorizationConfig: { signingRegion: "eu-west-1", signingServiceName: "states", }, endpoint: `https://states.eu-west-1.amazonaws.com`, name: "StepFunctionHTTPDataSource", // Providing the `serviceRole` now correctly DOESN'T throw a type error serviceRole, } ); ```
BackedDataSource make Grantable HttpDataSource. I think this pr allows better use of the iam config: #10171
fixes #11183