search

bifravst / e2e-bdd-test-runner-example

Example use of @bifravst/e2e-bdd-test-runner
https://github.com/bifravst/e2e-bdd-test-runner
Other
1 stars 0 forks source link

An in-range update of aws-cdk is breaking the build 🚨 #20

Closed greenkeeper[bot] closed 4 years ago

greenkeeper[bot] commented 4 years ago

There have been updates to the aws-cdk monorepo:

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the aws-cdk group definition.

aws-cdk is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **tests:** There are 1 failures, 0 warnings, and 0 notices.
Release Notes for v1.26.0

⚠ BREAKING CHANGES

  • apigateway: the interface now accepts endpointconfiguration property instead of endpoint type as defined by cfn
  • lambda-nodejs: parcel-bundler v1.x is now a peer dependency of @aws-cdk/aws-lambda-nodejs. Please add it to your package.json.

Features

  • apigateway: expose endpointconfiguration to include vpcEndpointIds (#6078) (99de6ca), closes #6038
  • apigateway: lambda request authorizer (#5642) (031932d)
  • appsync: mapping template for lambda proxy (#6288) (f865d5e)
  • batch: add JobQueue, ComputeEnvironment and JobDefinition constructs (c8a22b1)
  • cdk-assets: asset uploading tool (c505348)
  • cli: faster "no-op" deployments (#6346) (d4a132b), closes #6046 #2553 #6216
  • cfn: CloudFormation Resource Specification 11.1.0 (#6424) (ab9b77c)
  • cognito: user pool verification and invitation messages (#6282) (faf6693)
  • ecs-patterns: create dlq when queue is not provided for QueueProcessingService (#6356) (e307d7f)
  • kms: trustAccountIdentities avoids cyclic stack dependencies (03f4ef2)
  • rds: attach description to database secret (d5a4854)
  • sns: support multiple tokens as url and email subscriptions (#6357) (e5493bd), closes #3996
  • ssm: add ability to specify SSM Parameter tier (#6326) (9209ef6)

Bug Fixes

  • aws-ecs: propagate dnsTtl property part of cloudMapOptions (#6370) (747bdb2), closes #6223
  • cli: cdk deploy hangs when stack deployment fails (#6433) (4b11d99)
  • cli: Python init templates are missing .gitignore file (#6350) (cd6cd42), closes #5566
  • core: top-level resources cannot use long logical ids (#6419) (2a418b9), closes #6190 #6190
  • ecs: support file as firelens config type (#6322) (f9996f3)
  • lambda: erroneous inline code support for ruby (#6365) (8e21e78), closes #6302
  • lambda-nodejs: parcel is too big to bundle (a93e4d5), closes #6340
FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 4 years ago

After pinning to 1.25.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 4 years ago

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

Release Notes for v1.27.0

⚠ BREAKING CHANGES

  • cognito: UserPool.fromUserPoolAttributes() has been replaced
    by fromUserPoolId() and fromUserPoolArn().
  • cognito: IUserPool no longer contains userPoolProviderName
    and userPoolProviderUrl.
  • cognito: The property signInType of UserPool has been
    renamed to signInAliases and given a new type SignInAliases. The
    list of sign in types are now specified via boolean properties.
  • cognito: The property usernameAliasAttributes of UserPool has
    been dropped and its functionality merged with the signInAliases
    property.
  • cognito: The property autoVerifiedAttributes for UserPool is
    now renamed to autoVerify and its default has now changed. The new
    default is now determined by the value of signInAliases.
  • appsync: Configuration the user pool authorization is now done through the
    authorizationConfig property. This allows us to specify a default
    authorization mode out of the supported ones, currently limited to
    Cognito user pools and API keys.
  • custom-resources: physicalResourceId and physicalResourceIdPath
    were unified to a concrete type under the physicalResourceId property.
    Use PhysicalResourceId.fromResponse and PhysicalResourceId.of factory
    functions to specify it.

Features

Bug Fixes

  • assert: haveResourceLike and countResourcesLike compatibility (#6202) (86c04f3)
  • cli: fast "no-op" deploys do not consider tags (#6472) (5de87c1), closes #6463
  • codepipeline: an action's role imported in a different stack adds a dependency to the CodePipeline stack (#6458) (86ea564)
  • codepipeline: automatically named artifacts could contain illegal characters from stage/action names (#6460) (34aaca4)
  • core: adds enableVersionUpgrade property to CfnUpdatePolicy (#6434) (f8cacb9), closes #6158
  • custom-resources: AwsCustomResource with delete only action fails (#6363) (61a99e7), closes #6061
  • docker: cannot use cdk docker assets as base image (#6471) (983dd40), closes #6466
  • rds: setting timezone on DatabaseInstance causes internal failure (#6534) (9e2ac91), closes #6439
  • stepfunctions: valid reference path '$' fails with an error (#6483) (221c83b), closes #6388
greenkeeper[bot] commented 4 years ago

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

Release Notes for v1.28.0

⚠ BREAKING CHANGES

  • batch: computeEnvironments is now required
  • batch: the allocationStrategy property was moved from ComputeEnvironmentProps to the ComputeResources interface, which is where it semantically belongs.
  • custom-resources: getDataString was renamed to getResponseField.
  • custom-resources: getData was renamed to getResponseFieldReference.
  • custom-resources: catchErrorPattern was renamed to ignoreErrorCodesMatching. In addition, a few synth time validations were added when using this property. See Error Handling for details.
  • custom-resources: policyStatements property was removed in favor of a required policy property. Refer to Execution Policy for more details.

Features

Bug Fixes

  • apigateway: type mismatch in C# when setting identitySources (#6649) (2d3e7b1), closes #6538 40aws-cdk/aws-apigateway/test/authorizers/integ.request-authorizer.ts#L26
  • batch: computeEnvironments is now required for JobQueue (#6616) (0b6c865), closes #6615
  • batch: managed compute environment now properly works with compute resources and instanceRole has correct docstring and type definition (#6549) (4e81334)
  • certificatemanager: Route53 endpoint cannot be set and does not work for aws-cn (#6480) (9858cdb)
  • cli: codepipeline cloudformation action in cross account fail writing outputArtifacts (#6594) (05cf78b)
  • cloudwatch: missing LessThanLowerOrGreaterThanUpperThreshold (#6597) (9731555)
  • codepipeline-actions: use IBaseService instead of BaseService in EcsDeployActionProps (#6412) (bed5357)
  • eks: cannot upgrade version of clusters with an explicit name (#6064) (1dd7104)
  • eks: sporadic broken pipe when deploying helm charts (#6522) (03df1f1), closes #6381
  • iam: cannot add multiple conditions using same operator (348a952)
greenkeeper[bot] commented 4 years ago

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

Release Notes for v1.29.0

🚀 To enable new CDK projects such as CDK for Kubernetes, we have released the constructs programming model as an independent library called constructs. The @aws-cdk/core.Construct class is now a subclass of the base constructs.Construct.

⚠ BREAKING CHANGES

  • cognito: UserPoolAttribute has been removed. It is no longer
    required to defined a UserPool.
  • ec2: if you implemented a custom subclass of IMachineImage it must now always return a userData object.

Features

  • cli: add permissions to the bootstrap action role for cdk deploy (#6684) (52fd078)
  • codebuild: add support for Source Credentials (#6722) (a6e2d28)
  • cognito: user pool - custom & mandatory standard attributes (#6487) (6dfb677), closes #1747
  • cognito: user pool - MFA, password policy and email settings (#6717) (cc35dad)
  • core: the "constructs" module (#6623) (eded95b)
  • ec2: availabilityZone is optional when importing subnet (d10fe67), closes #6607
  • lambda-event-sources: failure handling for stream event sources (#5929) (5028009), closes #5236

Bug Fixes

  • aws-ecs-pattern: allow ScheduledTaskBase to run on a public subnet (#6624) (b9a1408), closes #6312
  • SecretValue.secretManager validates non-ARN ids do not contain : (#6371) (7cb8c3f)
  • aws-logs: remove validation of retentionInDays for unresolved tokens (#6727) (43a3420), closes #6690
  • ec2: MachineImages create appropriate UserData (7a10f0f)
greenkeeper[bot] commented 4 years ago

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

Release Notes for v1.30.0

Features

  • cloudwatch: standard set of graph colors (#6747) (97ae931)

Bug Fixes

greenkeeper[bot] commented 4 years ago

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

Release Notes for v1.31.0

⚠ BREAKING CHANGES

  • .NET Core v3.1 is required with JSII v1.1

Features

Bug Fixes

  • acm: Allow tokens as a part of the hosted zone name (#6685) (acfb6ef), closes #6133

  • aws-ecs-patterns: only create an A record if LB is public (#6895) (f31f4e1), closes #6702

  • cdk-assets: context path not honored by Docker asset build (#6957) (1edd507), closes #6954 #6814

  • cloudwatch: unhelpful error when reusing metric IDs (#6892) (60253a3)

  • cognito: user pool - link style email verification fails to deploy (#6938) (b5c60d5), closes #6811

  • ec2: spelling error in Instance's subnet selection logic. (#6752) (564561a)

  • iam: immutable role cannot be used as a construct (#6920) (56be032), closes #6885

  • .NET Core 3.1 is required with JSII v1.1 (#6951) (24f12d6)

greenkeeper[bot] commented 4 years ago

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

Release Notes for v1.32.0

⚠ BREAKING CHANGES

  • cognito: UserPoolClient construct no longer has the property
    userPoolClientClientSecret. The functionality to retrieve the client
    secret never existed in CloudFormation, so this property was not
    working in the first place.
  • cognito: The userPoolClientName property on the UserPoolClient
    construct will throw an error if client name was not configured on the
    UserPoolClient during initialization. This property was previously
    incorrectly configured and was returning a not-implemented message from
    CloudFormation every time.
  • amplify: use the sourceCodeProvider prop to connect your app to a source
    code provider. The props repository, accessToken and oauthToken do not exist
    anymore in AppProps.
  • kinesis: retentionPeriodHours is now retentionPeriod and of type Duration
  • eks: Cluster now creates a default managed nodegroup as its default capacity. Set the new cluster property defaultCapacityType to DefaultCapacityType.EC2 to preserve EC2 as its default capacity.
  • cognito: add*Trigger() methods to configure
    lambda triggers has now been replaced by a single
    addTrigger() method.
  • cognito: addTrigger() method will fail if a trigger
    was already configured for that user pool operation.

Features

Bug Fixes

  • acm-certificatemanager: DnsValidatedCertificateHandler support for SubjectAlternativeNames (#7050) (a711c01), closes #4659

  • aws-ecs-patterns: revert commit f31f4e1 (#6987) (0af2d2e)

  • aws-kinesis: test assume order between stacks (#7065) (17aab37)

  • cli: can't use credential providers for stacks with assets (#7022) (afd7045), closes #7005

  • cloudtrail: include s3KeyPrefix in bucket policy resource (#7053) (b49881f), closes #6741

  • cognito: user pool - passwordPolicy.minLength is not optional in all cases (#6971) (49cdd8f)

  • dynamodb: cannot use attribute as key in a GSI, non-key in another (#7075) (a6bd34f), closes #4398

  • ecs: default Service throws in a VPC without private subnets (#7188) (0ef6a95), closes #7062

  • events: Batch target does not work (#7191) (6f00783), closes #7137

  • kinesis: retention period does not use Duration type (#7037) (1186227), closes #7036

  • rewrite-imports: incorrect main in package.json (#7021) (2bf85b3)

  • stepfunctions-tasks: batch job - can not use task input as array size (#7008) (923d2a1), closes #6922

  • stepfunctions-tasks: confusion between multiple ways to run a Lambda (#6796) (7485448), closes #4801

  • cognito: clean up and document triggers (#6816) (32834cb)

greenkeeper[bot] commented 4 years ago

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

Release Notes for v1.32.0

⚠ BREAKING CHANGES

  • cognito: UserPoolClient construct no longer has the property
    userPoolClientClientSecret. The functionality to retrieve the client
    secret never existed in CloudFormation, so this property was not
    working in the first place.
  • cognito: The userPoolClientName property on the UserPoolClient
    construct will throw an error if client name was not configured on the
    UserPoolClient during initialization. This property was previously
    incorrectly configured and was returning a not-implemented message from
    CloudFormation every time.
  • amplify: use the sourceCodeProvider prop to connect your app to a source
    code provider. The props repository, accessToken and oauthToken do not exist
    anymore in AppProps.
  • kinesis: retentionPeriodHours is now retentionPeriod and of type Duration
  • eks: Cluster now creates a default managed nodegroup as its default capacity. Set the new cluster property defaultCapacityType to DefaultCapacityType.EC2 to preserve EC2 as its default capacity.
  • cognito: add*Trigger() methods to configure
    lambda triggers has now been replaced by a single
    addTrigger() method.
  • cognito: addTrigger() method will fail if a trigger
    was already configured for that user pool operation.

Features

Bug Fixes

  • acm-certificatemanager: DnsValidatedCertificateHandler support for SubjectAlternativeNames (#7050) (a711c01), closes #4659

  • aws-ecs-patterns: revert commit f31f4e1 (#6987) (0af2d2e)

  • aws-kinesis: test assume order between stacks (#7065) (17aab37)

  • cli: can't use credential providers for stacks with assets (#7022) (afd7045), closes #7005

  • cloudtrail: include s3KeyPrefix in bucket policy resource (#7053) (b49881f), closes #6741

  • cognito: user pool - passwordPolicy.minLength is not optional in all cases (#6971) (49cdd8f)

  • dynamodb: cannot use attribute as key in a GSI, non-key in another (#7075) (a6bd34f), closes #4398

  • ecs: default Service throws in a VPC without private subnets (#7188) (0ef6a95), closes #7062

  • events: Batch target does not work (#7191) (6f00783), closes #7137

  • kinesis: retention period does not use Duration type (#7037) (1186227), closes #7036

  • rewrite-imports: incorrect main in package.json (#7021) (2bf85b3)

  • stepfunctions-tasks: batch job - can not use task input as array size (#7008) (923d2a1), closes #6922

  • stepfunctions-tasks: confusion between multiple ways to run a Lambda (#6796) (7485448), closes #4801

  • cognito: clean up and document triggers (#6816) (32834cb)

greenkeeper[bot] commented 4 years ago

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

Release Notes for v1.32.1

Bug Fixes

  • iam: new IAM Condition type is unusable in Java (#7270) (85f606a)
greenkeeper[bot] commented 4 years ago

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

Release Notes for v1.32.2

Bug Fixes

  • cli: profile AssumeRole credentials don't work via proxy (#7292)
greenkeeper[bot] commented 4 years ago

Your tests are passing again with this update. Explicitly upgrade to these versions 🚀

Release Notes for v1.32.2

Bug Fixes

  • cli: profile AssumeRole credentials don't work via proxy (#7292)
github-actions[bot] commented 4 years ago

:tada: This issue has been resolved in version 1.0.7 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: