Skip to content

refactor: Parameterize remaining kagenti couplings post-rename #30

Description

@rubambiza

Summary

Cleanup pass: parameterize and rename the remaining kagenti couplings that still work via redirect today but will rot. No behavior change intended — this de-risks the next rename and removes stale references.

Work

  • Org defaults → rossoctl: dep-bump-scanner.sh, dep-bump-fixer.sh, automation-health-dashboard.sh. Add a --org NAME flag to link-health-fixer.sh, which currently hardcodes the org with no override (inconsistent with the others).
  • Hardcoded main-repo references: introduce a MAIN_REPO="rossoctl/rossoctl" and use it at the direct kagenti/kagenti API/PR sites in link-health-scanner.sh. Verify the dashboard's $ORG/$ORG references resolve correctly once the org default is rossoctl.
  • Org-neutral env/flag names: rename KAGENTI_DIR / --kagenti-dir / KAGENTI_REPO to a neutral MAIN_REPO_DIR (keep --kagenti-dir as a deprecated alias for one release). Keep the local clone-root default as-is (env-overridable) with a clarifying comment.
  • Tracking references: update epic/issue reference prefixes to rossoctl/rossoctl#… (issue numbers survive the rename).
  • Cosmetic: "kagenti org" headers, generated-by footers, and fixer signature strings. Batch these last.

Acceptance

  • No functional kagenti references remain in the scripts (redirect-dependent or otherwise); only intentional transition allowances (e.g. the dual-org link regex) stay, with a comment.
  • Dry-runs of all programs behave identically to before the cleanup.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions