-
Notifications
You must be signed in to change notification settings - Fork 2
Improve plan parser completeness and support optional() type defaults #46
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
andreacappelletti97
merged 3 commits into
c3xdev:main
from
Tyron2k:fix/plan-parser-and-hcl-optional-defaults
Jul 22, 2026
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Appending pure-delete resources into the same
outslice the calculator prices means they land inPROJECT TOTAL— which regresses the #52 semantics:estimate plan.jsonwithout--show-deltanow counts resources that won't exist post-apply.Repro with a plan of {create t3.small, no-op t3.micro, delete t3.medium}: PROJECT TOTAL prints $53.14, but the post-apply fleet is $22.77 (the two survivors).
--show-deltashows the same inflated $53.14.Deletes shouldn't contribute to the post-apply total, and shouldn't appear at all in the non-delta view. Suggest surfacing them to the delta renderer via a separate field (or excluding
PlanActionDeletefrom the priced total) so the-marker and the DELTA line keep working while PROJECT TOTAL stays the post-apply fleet.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch — you're right, appending deletes into
outbroke the #52 semantics. Fixed in 63b6d0f:NewEstimatenow skipsPlanActionDeletewhen summingProjectTotal--show-delta)+/~/-) scoped to delta mode only — normal view has no prefixesVerified with your repro scenario:
estimate plan.jsonshows only the two survivors,--show-deltashows all three with correct markers and a separate DELTA line.