Skip to content

docs(changelog): record the #2206 and #2211 fixes #2220

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.

Sign up for GitHub

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
cristim merged 2 commits into from
Oct 16, 2026
Merged

docs(changelog): record the #2206 and #2211 fixes #2220

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
101449a
docs(changelog): record the #2206 and #2211 fixes
cristim Oct 16, 2026
a0d96b0
docs(changelog): note ProjectedCoverage needs known existing coverage
cristim Oct 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,21 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/).

### Fixed

- `configure-gcp`: skipping (or giving an unknown answer at) the "Create Service
Account" step no longer continues with the default
`cudly-service-account@<project>` email that was never created. The wizard now
asks for the existing service account email, validates it as a
`*.gserviceaccount.com` address, and uses it for the role grant and key steps
(#2211).
- When `--max-instances`, `--count-override` or the duplicate-RI check lowers a
recommendation's count, `ProjectedCoverage` and `ProjectedUtilization` are
re-derived for the new count instead of reporting the figures sized for the
original count. This applies to RI rows with a usage signal;
`ProjectedCoverage` is only re-derived when existing coverage is known.
Savings Plans and projections that were never computed are left as they are.
The Redshift `NumberOfNodes` now follows the count, including after
`--coverage` and `--target-coverage` sizing. RDS `ProjectedCoverage` is a
family-wide figure and is not re-derived yet; see issue #2214 (#2206).
- An explicit `--output` path that already exists (file, directory or symlink)
is now refused during validation instead of being silently truncated. Choose a
new path or remove the old file; scripts that reuse one path must do the same.
Expand Down
Loading