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

[NEW EXAMPLE] AWS CDK - Diff computation #5

Closed
ainzzorl opened this issue Jul 9, 2021 · 3 comments
Closed

[NEW EXAMPLE] AWS CDK - Diff computation #5

ainzzorl opened this issue Jul 9, 2021 · 3 comments
Labels
new example New example proposal

Comments

@ainzzorl
Copy link
Owner

ainzzorl commented Jul 9, 2021

General

  • Project name: AWS CDK
  • Example name: Compute diff between infrastructure templates
  • Project home page: https://github.com/aws/aws-cdk
  • Programming language(s): Typescript
  • Frameworks, libraries used: AWS, CloudFormation

Description

AWS CDK is an infrastructure-as-code tool. When updating infrastructure, it needs to compute semantic diff between infrastructure templates. The algorithm is rather straightforward.

Links

What makes it interesting

  • Computing meaningful diffs is a rather common problem.
  • Testing is exemplary.

Other

N/A

@ainzzorl ainzzorl added the new example New example proposal label Jul 9, 2021
@ainzzorl
Copy link
Owner Author

Before publishing:

  • Remove "Give a high-level description of the project. Explain the part(s) of it that include the example in more detail."
  • "The diff can be visualized." - maybe "There's a method to print the diff in a human-readable format"?
  • Main method - explain about the convergence. And in general how it works, it's not obviously clear.
  • "Diffing templates (without propagation)" - mention DIFF_HANDLERS doing the heavy lifting.
  • Add observations or remove.
  • Note that some resource types require special treatment (network, IAM).
  • Mention impact types.
  • Mention that we are just scratching the surface here.

@ainzzorl
Copy link
Owner Author

Updated and set the status to PUBLISHED. It is still one of the weaker articles, though. Some explanations are lacking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new example New example proposal
Projects
None yet
Development

No branches or pull requests

1 participant