Skip to content

feat(providers/aws): rich self-describing RI display names (closes #687) - #806

Merged
cristim merged 1 commit into
feat/multicloud-web-frontendfrom
fix/687-wave4
Jun 5, 2026
Merged

cristim merged 1 commit into
feat/multicloud-web-frontendfrom
fix/687-wave4

Conversation

@cristim

@cristim cristim commented May 28, 2026 •

Copy link
Copy Markdown
Member

Summary

  • EC2: tagReservedInstance now stamps a self-describing Name tag using BuildReservationName (format ec2-{region}-{sku}-{count}x-{term}-{paymt}-{ts}-{rand}). EC2 PurchaseReservedInstancesOfferingInput has no customer-supplied name field, so the Name tag is the only way to identify the RI in the AWS console without querying CUDly's purchase history. Count, Term, and PaymentOption descriptor tags are also added to match the Redshift tag set.
  • Redshift: tagReservedNode gains the same Name tag via BuildReservationName (format redshift-{region}-{sku}-...). Same rationale: no customer-supplied ID on PurchaseReservedNodeOfferingInput.
  • RDS / ElastiCache / MemoryDB / OpenSearch: already wired to BuildReservationName as the customer-supplied reservation ID in prior work on this branch; no changes needed.
  • Also fixes 3 pre-existing test compile errors (findOfferingID called with 2 args instead of 3 in rds and redshift test files).

Format

{svc}-{region}-{sku}-{count}x-{term}-{paymt}-{ts}-{rand} (60-char cap via BuildReservationName in pkg/common), e.g.:

ec2-us-west-2-m5-xlarge-3x-1yr-allup-20260522T190000-a1b2c3d4
redshift-eu-central-1-ra3-4xlarge-1x-1yr-noup-20260522T190000-a1b2c3d4

Services wired (7 total)

Service Mechanism
EC2 Name tag in tagReservedInstance (post-purchase CreateTags)
Redshift Name tag in tagReservedNode (post-purchase CreateTags)
RDS rich ReservedDBInstanceId (already done in branch)
ElastiCache rich ReservedCacheNodeId (already done in branch)
MemoryDB rich ReservationId (already done in branch)
OpenSearch rich ReservationName (already done in branch)
Savings Plans N/A (SP uses a UUID offering ID; no per-purchase name field)

Test plan

  • go build ./... passes (verified locally)
  • TestClient_tagReservedInstance_NameTagPresent - asserts Name tag present and self-describing on EC2 CreateTags call
  • TestClient_PurchaseCommitment_NameTagInCreateTagsRequest - end-to-end EC2 purchase asserts Name tag in CreateTags
  • TestClient_tagReservedNode_NameTagPresent - asserts Name tag present on Redshift CreateTags call
  • TestClient_PurchaseCommitment_TagsCarryRichDescriptors (extended) - asserts Name tag starts with "redshift" in addition to Count/Term/PaymentOption
  • All 425 tests in affected packages pass (ec2, redshift, rds, elasticache, memorydb, opensearch, pkg/common)

EC2 and Redshift reserved-instance purchases now stamp a Name tag with
the rich {svc}-{region}-{sku}-{count}x-{term}-{paymt}-{ts}-{rand}
format already used by the other AWS services for their customer-
supplied reservation IDs (RDS/ElastiCache/MemoryDB/OpenSearch).

EC2 PurchaseReservedInstancesOfferingInput has no customer-supplied ID
field and Redshift PurchaseReservedNodeOfferingInput has none either,
so the Name tag is the only way to identify these commitments in the
AWS console without cross-referencing CUDly. Count/Term/PaymentOption
descriptor tags are also added to EC2 to match the Redshift tag set.

Also fixes three pre-existing test compile errors (findOfferingID
called with 2 args instead of the required 3 in rds and redshift
test files).
@cristim cristim added triaged Item has been triaged priority/p2 Backlog-worthy severity/medium Moderate harm urgency/eventually No deadline impact/many Affects most users effort/m Days type/feat New capability labels May 28, 2026
@coderabbitai

coderabbitai Bot commented May 28, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@cristim, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 6 minutes and 23 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 72a14f55-1a00-4ac0-ab9c-e1fc5240b14b

📥 Commits

Reviewing files that changed from the base of the PR and between 4956d66 and bd68fd9.

📒 Files selected for processing (5)
  • providers/aws/services/ec2/client.go
  • providers/aws/services/ec2/client_test.go
  • providers/aws/services/rds/client_test.go
  • providers/aws/services/redshift/client.go
  • providers/aws/services/redshift/client_test.go
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/687-wave4

Comment @coderabbitai help to get the list of available commands and usage tips.

@cristim

cristim commented May 28, 2026

Copy link
Copy Markdown
Member Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented May 28, 2026

Copy link
Copy Markdown
Contributor
✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@cristim

cristim commented May 30, 2026

Copy link
Copy Markdown
Member Author

@coderabbitai full review

@coderabbitai

coderabbitai Bot commented May 30, 2026

Copy link
Copy Markdown
Contributor
✅ Actions performed

Full review triggered.

@cristim

cristim commented Jun 4, 2026

Copy link
Copy Markdown
Member Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Rate Limit Exceeded

@cristim have exceeded the limit for the number of chat messages per hour. Please wait 38 minutes and 51 seconds before sending another message.

@cristim

cristim commented Jun 5, 2026

Copy link
Copy Markdown
Member Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jun 5, 2026 •

Copy link
Copy Markdown
Contributor
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@cristim

cristim commented Jun 5, 2026

Copy link
Copy Markdown
Member Author

@coderabbitai full review

@coderabbitai

coderabbitai Bot commented Jun 5, 2026 •

Copy link
Copy Markdown
Contributor
✅ Action performed

Full review finished.

@cristim
cristim merged commit 57a6cf9 into feat/multicloud-web-frontend Jun 5, 2026
4 checks passed
@cristim
cristim deleted the fix/687-wave4 branch July 27, 2026 11:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

effort/m Days impact/many Affects most users priority/p2 Backlog-worthy severity/medium Moderate harm triaged Item has been triaged type/feat New capability urgency/eventually No deadline

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant