Skip to content

feat(cdk-cli-wrapper): add progress argument for cdk deploy #21762

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

Merged
merged 2 commits into from
Aug 25, 2022
Merged

feat(cdk-cli-wrapper): add progress argument for cdk deploy #21762

merged 2 commits into from
Aug 25, 2022

Conversation

corymhall
Copy link
Contributor

Adding the ability to specify --progress when using cdk deploy. I'm
setting the default to events as opposed to the default of bar in
the CLI. Since this library is currently only used in the integ-runner,
and if published will most likely be used in automation I think it makes
more sense to set progress to events.

This is really useful when running multiple integration tests in
parallel. If set to bar (CLI default) the logs will overlap/overwrite
each other which makes it difficult to troubleshoot.


All Submissions:

Adding new Unconventional Dependencies:

  • This PR adds new unconventional dependencies following the process described here

New Features

  • Have you added the new feature to an integration test?
    • Did you use yarn integ to deploy the infrastructure and generate the snapshot (i.e. yarn integ without --dry-run)?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Sorry, something went wrong.

Adding the ability to specify `--progress` when using cdk `deploy`. I'm
setting the default to `events` as opposed to the default of `bar` in
the CLI. Since this library is currently only used in the integ-runner,
and if published will most likely be used in automation I think it makes
more sense to set progress to `events`.

This is really useful when running multiple integration tests in
parallel. If set to `bar` (CLI default) the logs will overlap/overwrite
each other which makes it difficult to troubleshoot.
@gitpod-io
Copy link

gitpod-io bot commented Aug 25, 2022

@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Aug 25, 2022
@aws-cdk-automation aws-cdk-automation requested a review from a team August 25, 2022 18:40
@github-actions github-actions bot added the p2 label Aug 25, 2022
@TheRealAmazonKendra TheRealAmazonKendra added pr-linter/exempt-readme The PR linter will not require README changes pr-linter/exempt-integ-test The PR linter will not require integ test changes labels Aug 25, 2022
@mergify
Copy link
Contributor

mergify bot commented Aug 25, 2022

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: 90330e2
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify mergify bot merged commit dab83cc into aws:main Aug 25, 2022
@mergify
Copy link
Contributor

mergify bot commented Aug 25, 2022

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

josephedward pushed a commit to josephedward/aws-cdk that referenced this pull request Aug 30, 2022
)

Adding the ability to specify `--progress` when using cdk `deploy`. I'm
setting the default to `events` as opposed to the default of `bar` in
the CLI. Since this library is currently only used in the integ-runner,
and if published will most likely be used in automation I think it makes
more sense to set progress to `events`.

This is really useful when running multiple integration tests in
parallel. If set to `bar` (CLI default) the logs will overlap/overwrite
each other which makes it difficult to troubleshoot.


----

### All Submissions:

* [ ] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md)

### Adding new Unconventional Dependencies:

* [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies)

### New Features

* [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)?
	* [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)?

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution/core This is a PR that came from AWS. p2 pr-linter/exempt-integ-test The PR linter will not require integ test changes pr-linter/exempt-readme The PR linter will not require README changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants