Introduce a new Cloudera Runtime (CR) version in Cloudbreak and later make it the default — Data Lake + Data Hub blueprints, cluster templates, application.yml runtime properties, upgrade matrix, and the tests that must be bumped. Use when Release Engineering…
Triage Cloudbreak pull request GitHub Actions failures from a PR number — unit tests, Jacoco coverage, checkstyle, SpotBugs, integration tests, and related PR checks. Use when a PR is red, CI failed, checks failed, or the user gives a PR number and asks why…
Review Cloudbreak pull requests the way the team actually reviews them, distilled from the team's real review history. Use when reviewing a PR/diff, or to self-review before requesting review.
Jira Cloud conventions for Cloudbreak — project keys, Team field (customfield_10001), JQL with Atlassian team ids, mascot clan → module mapping, quarterly epic labels.
Operate read-first against AWS, Azure, and optionally GCP from the terminal or cloud MCP tools—instances by region, related compute/network resources, and troubleshooting. For Cloudbreak work in cloud-aws-*, cloud-azure, cloud-gcp modules.
Add a database schema migration in Cloudbreak using MyBatis Migrations — correct file location, timestamp+ticket naming, the mandatory @UNDO section, and idempotent/reversible DDL. Use when changing the schema of…
Add or modify a Cloudbreak flow — state machine config, states/events enums, actions, handlers, and flow chains — without deadlocking the engine. Use when implementing any long-running async operation (provisioning, upgrade, repair, scaling, rotation) in…
Write and run tests in Cloudbreak — JUnit 5 + Mockito unit tests, Spring integration tests, the mandatory authorization-annotation compliance test, flow-chain graph tests, plus Gradle/jacoco commands and coverage gates. Use when adding tests, reproducing a…