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

Correctly account for CDK::Metadata resource in cdk diff` #435

Merged
merged 1 commit into from
Jul 30, 2018

Conversation

RomainMuller
Copy link
Contributor

The arguments to the diff function were passed incorrectly, resulting in
the version tracking information not being forwarded correctly to
synthesizeTemplate.

Fixes #422

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

The arguments to the diff function were passed incorrectly, resulting in
the version tracking information not being forwarded correctly to
synthesizeTemplate.

Fixes #422
@RomainMuller RomainMuller requested review from eladb and rix0rrr and removed request for eladb July 30, 2018 15:14
const toolkitStackName = completeConfig().get(['toolkitStackName']) || DEFAULT_TOOLKIT_STACK_NAME;
const trackVersions = completeConfig().get(['versionReporting']);
const toolkitStackName: string = completeConfig().get(['toolkitStackName']) || DEFAULT_TOOLKIT_STACK_NAME;
const trackVersions: boolean = completeConfig().get(['versionReporting']);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this mean in terms of disabling version reporting via cdk.json? I think this should be:

{
  "version-reporting": false
}

And not versionReporting (I am okay with allowing both)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kebab-case (version-reporting) in the JSON feels... weird. Also, if version-reporting, then toolkit-stack-name.

Allowing both feels... messy (then we want to check if we got both at the same time, and err if they disagree with each other... feels like an un-necessary evil).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, let's leave it versionReporting (although I like my reservation to be recorded for posterity).

@RomainMuller RomainMuller merged commit 5a1a277 into master Jul 30, 2018
@RomainMuller RomainMuller deleted the rmuller/fix-cdk-diff-md branch July 30, 2018 16:24
@NGL321 NGL321 added the contribution/core This is a PR that came from AWS. label Sep 27, 2019
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.

"cdk diff" doesn't take the CDK::Metadata resource into account
3 participants