AWS → Azure Feature Parity Gaps · Issue #473 · LeanerCloud/cloud-commitments-cli · GitHub
Skip to content

AWS → Azure Feature Parity Gaps #473

Closed
Closed
AWS → Azure Feature Parity Gaps#473
Labels
Post Launch Feature Parity AnalysisPost-launch review of feature parity across cloud providerseffort/lWeeksimpact/all-usersAffects every userpriority/p2Backlog-worthyseverity/mediumModerate harmtriagedItem has been triagedtype/featNew capabilityurgency/this-sprintWithin the current sprint

Description

@rocketri
rocketri
opened on May 15, 2026

Summary

This issue tracks the feature parity gaps between the AWS and Azure provider implementations, identified via static analysis of the codebase.

Services Covered

Domain AWS Azure
Compute EC2 Compute (VMs)
Relational DB RDS Database (Azure SQL)
Cache ElastiCache Cache (Redis)
NoSQL (none) CosmosDB
Search OpenSearch Implemented but unreachable (see below)
Data Warehouse Redshift (missing)
In-memory DB MemoryDB (missing)
Savings Plans SavingsPlans (missing)

Gaps: Azure Behind AWS

Feature AWS Azure
Multi-account (Organizations) Yes — enumerates org accounts automatically No — GetAccounts discovers subscriptions but GetServiceClient only operates on one at a time
Savings Plans Yes No
Data Warehouse (Redshift) Yes No Azure Synapse equivalent
MemoryDB Yes No
Convertible RI exchange Yes (EC2 only) — ListConvertibleReservedInstances, FindConvertibleOfferings No
RI Utilization reporting Yes — GetRIUtilization via Cost Explorer No

Bug: Azure Search Client is Dead Code

providers/azure/services/search/ is fully implemented (GetRecommendations, GetExistingCommitments, PurchaseCommitment, ValidateOffering, GetOfferingDetails, GetValidResourceTypes) but is never reachable — GetSupportedServices() and GetServiceClient() in providers/azure/provider.go have no reference to it.

It needs to be wired up:

  1. Add common.ServiceSearch to the GetSupportedServices() return slice
  2. Add a case common.ServiceSearch: branch in GetServiceClient() returning NewSearchClient(...)

Azure-Only (AWS gaps)

  • CosmosDB — no AWS NoSQL equivalent in CUDly
  • Azure Search — once wired up, AWS OpenSearch is the counterpart

Notes

  • All service clients that are implemented (both providers) share the full ServiceClient interface: GetRecommendations, GetExistingCommitments, PurchaseCommitment, ValidateOffering, GetOfferingDetails, GetValidResourceTypes
  • Azure tags reservations inline at purchase time (embedded in the PUT body); AWS EC2/OpenSearch/Redshift make a separate tagging call post-purchase — this is parity via different mechanisms, not a gap
  • GetRIUtilization is an AWS-specific extension explicitly outside the provider.RecommendationsClient interface

Activity

  1. rocketri
    added
    Post Launch Feature Parity AnalysisPost-launch review of feature parity across cloud providers
    on May 15, 2026
  2. cristim
    added
    type/featNew capability
    priority/p2Backlog-worthy
    severity/mediumModerate harm
    urgency/this-sprintWithin the current sprint
    impact/all-usersAffects every user
    effort/lWeeks
    triagedItem has been triaged
    on May 19, 2026

  3. cristim commented on May 20, 2026

    @cristim
    cristim
    on May 20, 2026
    Member

    Sub-issues Filed

    This meta-tracker has been split into the following triaged sub-issues:

    Gap Sub-issue
    Azure multi-account (Subscriptions) #553
    Azure Savings Plans #554
    Azure Synapse data warehouse #555
    Azure in-memory database (Cache for Redis) #556
    Azure RI exchange #557
    Azure RI utilization reporting #558
    AWS NoSQL service support #559

    See individual issues for detailed scope, acceptance criteria, and suggested approaches.

  4. cristim commented on May 20, 2026

    @cristim
    cristim
    on May 20, 2026
    Member

    PR #560 addresses the Azure Search wiring sub-task: GetSupportedServices() now includes ServiceSearch and GetServiceClient() dispatches to NewSearchClient(). Also fixed the pre-existing ServiceOther misclassification in the search client itself.

    Remaining open gaps from the original analysis (not addressed by #560):

    • CosmosDB client service type (check if it also returns ServiceOther vs ServiceNoSQL)
    • Any other service clients not yet wired (check the issue description for the full list)
    • The GetValidResourceTypes / ValidateOffering patterns may need integration testing once the client is reachable

  5. cristim commented on May 20, 2026

    @cristim
    cristim
    on May 20, 2026
    Member

    Status update on the 7 split-out sub-issues:

    Plus PR for the Azure Search wiring sub-task is in flight under separate branch fix/issue-473-azure-search-wiring.

  6. cristim
    added 4 commits that reference this issue on May 20, 2026

    feat(providers/azure): add RI utilization reporting (closes #558) (#563)

    cc465d0

    feat(azure/ri-exchange): list exchangeable Azure VM reservations (refs …

    bc81d15

    feat(azure): multi-subscription enumeration parity with AWS Organizat…

    9dafc22

    feat(azure/savings-plans): provider client + dispatch wiring (refs #473)

    0ee4c66

  7. 2 remaining items

  8. cristim
    added 9 commits that reference this issue on May 20, 2026

    fix(providers/azure): wire Azure Search client into provider (closes #…

    b935726

    feat(providers/azure/synapse): add data-warehouse service client (closes

    ad068a9

    feat(azure/savings-plans): provider client + dispatch wiring (refs #473…

    e09d0a7

    fix(providers/azure): wire Azure Search client into provider (closes #…

    519347e

    feat(providers/azure/synapse): add data-warehouse service client (closes

    3777bb8

    feat(providers/azure/synapse): add data-warehouse service client (closes

    84244b1

    fix(providers/azure): wire Azure Search client into provider (closes #…

    0ea02d1

    feat(providers/azure/synapse): add data-warehouse service client (closes

    dc2ee71

    fix(providers/azure): wire Azure Search client into provider (closes #…

    89e8c02
  9. cristim
    added a commit that references this issue on Jun 5, 2026

    fix(providers/azure): wire Azure Search client into provider (closes #…

    aaee6a5
  10. cristim
    closed this as completedin aaee6a5on Jun 9, 2026
  11. cristim
    added 2 commits that reference this issue on Jul 27, 2026

    feat(azure/compute): CalculateExchange and DoExchange client operations

    c5a2692

    feat(azure/ri-exchange): find compatible offerings and execute exchan…

    ecb0681
  12. cristim
    added 2 commits that reference this issue on Sep 27, 2026

    feat(azure/ri-exchange): list exchangeable Azure VM reservations (refs …

    5413279

    feat(azure/savings-plans): provider client + dispatch wiring (refs #473…

    15fe3d5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Post Launch Feature Parity AnalysisPost-launch review of feature parity across cloud providerseffort/lWeeksimpact/all-usersAffects every userpriority/p2Backlog-worthyseverity/mediumModerate harmtriagedItem has been triagedtype/featNew capabilityurgency/this-sprintWithin the current sprint

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions