Automatically link Harness CCM recommendations to Jira — and make your cloud cost management smarter, faster, and a lot more fun! 😎
You'll need a CSV file to define how your Cost Category buckets map to JIRA configurations. Here’s the format:
<Bucket>,<JIRA Project>,<Recommendation Issue Type>,<Anomaly Issue Type>,<Reporter>
Set the Cost Category to use for the bucket definitions using the COST_CATEGORY
environment variable. 📦
Whenever a recommendation falls under a bucket listed in your CSV for the given Cost Category, a shiny new Jira item will be created, matching the spec from that line. ✨
Set these environment variables to get rolling:
CSV_FILE
: Path to your mapping of buckets to JIRA configuration 🗂️JIRA_CONNECTOR_REF
: Connector ID of your JIRA connector (must start withaccount.
) 🔗COST_CATEGORY
: Cost category name for which buckets are searched from 💸HARNESS_URL
: URL of your Harness instance (e.g.,app.harness.io
) 🌐HARNESS_ACCOUNT_ID
: Harness account ID (e.g.,xyz123
) 🆔HARNESS_PLATFORM_API_KEY
: Harness API key (e.g.,sat.xyz123.XXXXXXXXX
) 🔑MIN_SAVINGS
: (Optional) Minimum monthly savings in USD for a recommendation to be processed (e.g.,10.0
for $10) 💰
💡 Pro tip: Keep your CSV and environment variables up to date to ensure smooth automation!
Happy automating! 🤖✨