apigatewayv2-authorizers: The default value for the prop authorizerName
in HttpJwtAuthorizerProps has changed.
apigatewayv2-authorizers:HttpJwtAuthorizer now takes the
construct id and the target jwt issuer as part of its constructor.
apigatewayv2-authorizers:HttpLambdaAuthorizer now takes
the construct id and the target lambda function handler as part of
its constructor.
apigatewayv2-authorizers: The default value for the prop
authorizerName in HttpUserPoolAuthorizerProps has changed.
apigatewayv2: The HttpIntegration and WebSocketIntegration
classes require an "id" parameter to be provided during its initialization.
apigatewayv2-integrations: The LambdaWebSocketIntegration is now
renamed to WebSocketLambdaIntegration. The new class accepts the
handler to the target lambda function directly in its constructor.
apigatewayv2-integrations:HttpProxyIntegration and
HttpProxyIntegrationProps are now renamed to HttpUrlIntegration
and HttpUrlIntegrationProps respectively. The new class accepts the
target url directly in its constructor.
apigatewayv2-integrations:LambdaProxyIntegration and
LambdaProxyIntegrationProps are now renamed to
HttpLambdaIntegration and HttpLambdaIntegrationProps respectively.
The new class accepts the lambda function handler directly in its
constructor.
apigatewayv2-integrations:HttpAlbIntegration now accepts the
ELB listener directly in its constructor.
apigatewayv2-integrations:HttpNlbIntegration now accepts the
ELB listener directly in its constructor.
apigatewayv2-integrations:HttpServiceDiscoveryIntegration now
accepts the service discovery Service directly in its constructor.
apigatewayv2-authorizers:UserPoolAuthorizerProps is now
renamed to HttpUserPoolAuthorizerProps.
apigatewayv2: The interface IHttpRouteIntegration is replaced by
the abstract class HttpRouteIntegration.
apigatewayv2: The interface IWebSocketRouteIntegration is now
replaced by the abstract class WebSocketRouteIntegration.
apigatewayv2: Previously, we allowed the usage of integration
classes to be used with routes defined in multiple HttpApi instances
(or WebSocketApi instances). This is now disallowed, and separate
instances must be created for each instance of HttpApi or
WebSocketApi.
apigatewayv2-authorizers: The default value for the prop authorizerName
in HttpJwtAuthorizerProps has changed.
apigatewayv2-authorizers:HttpJwtAuthorizer now takes the
construct id and the target jwt issuer as part of its constructor.
apigatewayv2-authorizers:HttpLambdaAuthorizer now takes
the construct id and the target lambda function handler as part of
its constructor.
apigatewayv2-authorizers: The default value for the prop
authorizerName in HttpUserPoolAuthorizerProps has changed.
apigatewayv2: The HttpIntegration and WebSocketIntegration
classes require an "id" parameter to be provided during its initialization.
apigatewayv2-integrations: The LambdaWebSocketIntegration is now
renamed to WebSocketLambdaIntegration. The new class accepts the
handler to the target lambda function directly in its constructor.
apigatewayv2-integrations:HttpProxyIntegration and
HttpProxyIntegrationProps are now renamed to HttpUrlIntegration
and HttpUrlIntegrationProps respectively. The new class accepts the
target url directly in its constructor.
apigatewayv2-integrations:LambdaProxyIntegration and
LambdaProxyIntegrationProps are now renamed to
HttpLambdaIntegration and HttpLambdaIntegrationProps respectively.
The new class accepts the lambda function handler directly in its
constructor.
apigatewayv2-integrations:HttpAlbIntegration now accepts the
ELB listener directly in its constructor.
apigatewayv2-integrations:HttpNlbIntegration now accepts the
ELB listener directly in its constructor.
apigatewayv2-integrations:HttpServiceDiscoveryIntegration now
accepts the service discovery Service directly in its constructor.
apigatewayv2-authorizers:UserPoolAuthorizerProps is now
renamed to HttpUserPoolAuthorizerProps.
apigatewayv2: The interface IHttpRouteIntegration is replaced by
the abstract class HttpRouteIntegration.
apigatewayv2: The interface IWebSocketRouteIntegration is now
replaced by the abstract class WebSocketRouteIntegration.
apigatewayv2: Previously, we allowed the usage of integration
classes to be used with routes defined in multiple HttpApi instances
(or WebSocketApi instances). This is now disallowed, and separate
instances must be created for each instance of HttpApi or
WebSocketApi.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot]
commented
2 years ago
Bumps @aws-cdk/core from 1.101.0 to 1.135.0.
Release notes
Sourced from
@aws-cdk/core's releases.... (truncated)
Changelog
Sourced from
@aws-cdk/core's changelog.... (truncated)
Commits
ed4a4b4fix(iam): AWS Managed Policy ARNs are not deduped (#17623)919605achore: npm-check-updates && yarn upgrade (#17909)d64057ffeat(core): add applyRemovalPolicy to IResource (#17746)6c7550bchore: npm-check-updates && yarn upgrade (#17687)cda6601fix(core): bundling skipped with --exclusively option and stacks under stage ...a90e959fix(assets): SAM asset metadata missing from log retention and custom resourc...3721358feat: warn users when deprecated elements are used (#17328)19322b4chore: npm-check-updates && yarn upgrade (#17525)4ba40dcfix(NestedStack): add asset metadata to NestedStack resources for local tooli...1afc56cchore: npm-check-updates && yarn upgrade (#17453)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)