Skip to content

Conversation

sandyydk
Copy link
Contributor

@sandyydk sandyydk commented Jul 8, 2025

Screenshot 2025-07-08 at 10 58 31 PM

This pull request introduces a new feature for fetching commitment coverage information in the Harness Cloud Cost Management (CCM) toolset. The changes include updates to the API, data structures, and tool registration to support this functionality.

New Feature: Commitment Coverage Retrieval

  • Added API Endpoint and Constants:

    • Introduced ccmCommitmentBasePath and ccmCommitmentCoverageDetailsPath constants for the new API endpoint to fetch commitment coverage details. (client/cloudcostmanagement.go)
  • New Method in CloudCostManagementService:

    • Implemented GetComputeCoverage method to handle API requests for commitment coverage, including default date handling and optional parameters like service and cloud account IDs. (client/cloudcostmanagement.go)

Data Structure Enhancements

  • Added DTOs for Commitment Coverage:
    • Introduced CCMCommitmentOptions, CCMCommitmentBaseResponse, and CCMCommitmentAPIFilter structs to represent request and response data for the new feature. (client/dto/cloudcostmanagement.go) [1] [2]

Tool Registration and Documentation

  • New Tool for Commitment Coverage:

    • Added FetchCommitmentCoverageTool to define and handle the new CLI tool for fetching commitment coverage, including parameter validation and response formatting. (pkg/harness/cloudcostmanagement.go)
  • Registered the Tool:

    • Registered FetchCommitmentCoverageTool in the registerCloudCostManagement function to make it available in the toolset. (pkg/harness/tools.go)
  • Documentation Update:

    • Updated the README.md to include the new get_commitment_coverage command in the list of available tools. (README.md)

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@sandyydk sandyydk requested a review from vistaarjuneja July 8, 2025 17:32
@bot2-harness bot2-harness deleted the comm-orch branch July 9, 2025 16:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants