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

feat(toolkit): by default hide AWS::CDK::Metadata from "cdk diff" #1186

Merged
merged 3 commits into from
Nov 18, 2018

Conversation

eladb
Copy link
Contributor

@eladb eladb commented Nov 15, 2018

DifferenceCollection#applyFilter can be used to delete any changes
that do not pass the predicate from the collection.

Changed DifferenceCollection#count to do a lazy calculation since now
changes is mutable.

The toolkit switch cdk diff --strict disables this behavior.

Fixes #465

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

`DifferenceCollection#applyFilter` can be used to delete any changes
that do not pass the predicate from the collection.

Changed `DifferenceCollection#count` to do a lazy calculation since now
`changes` is mutable.

The toolkit switch `cdk diff --strict` disables this behavior.

Fixes #465
@eladb eladb merged commit ef0017a into master Nov 18, 2018
@eladb eladb deleted the benisrae/hide-metadata-resource branch November 19, 2018 12:30
@NGL321 NGL321 added the contribution/core This is a PR that came from AWS. label Sep 23, 2019
@mergify
Copy link
Contributor

mergify bot commented Sep 23, 2019

Thanks so much for taking the time to contribute to the AWS CDK ❤️

We will shortly assign someone to review this pull request and help get it
merged. In the meantime, please take a minute to make sure you follow this
checklist
:

  • PR title type(scope): text
    • type: fix, feat, refactor go into CHANGELOG, chore is hidden
    • scope: name of module without aws- or cdk- prefix or postfix (e.g. s3 instead of aws-s3-deployment)
    • text: use all lower-case, do not end with a period, do not include issue refs
  • PR Description
    • Rationale: describe rationale of change and approach taken
    • Issues: indicate issues fixed via: fixes #xxx or closes #xxx
    • Breaking?: last paragraph: BREAKING CHANGE: <describe what changed + link for details>
  • Testing
    • Unit test added. Prefer to add a new test rather than modify existing tests
    • CLI or init templates change? Re-run/add CLI integration tests
  • Documentation
    • README: update module README to describe new features
    • API docs: public APIs must be documented. Copy from official AWS docs when possible
    • Design: for significant features, follow design process

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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Toolkit: diff shows version bump even if nothing else changed
4 participants