Skip to content

enhancement(cli): cleaner wrapper logging and commentary #253

Description

@kopardev

Summary

Improve CARLISLE wrapper CLI output so users can quickly understand current phase, status, and next actions.

Problem

Current wrapper output is functional but inconsistent in formatting and message intent, making it harder to scan during init/dryrun/run and harder to recover from errors quickly.

Scope

  • Standardize user-facing output style (for example: INFO/STEP/WARN/ERROR/OK patterns)
  • Make phase transitions explicit (preflight, dryrun, submission, completion/failure)
  • Improve actionable error text for common setup/run failures
  • Keep implementation in existing wrapper logic only

Requirement

No extra files should be created as part of implementation.

Acceptance Criteria

  • User-facing wrapper output is consistently formatted and easier to scan
  • Submission and monitoring guidance is clearly printed for run mode
  • Error messages include concrete next-step remediation
  • Existing run behavior is preserved; output clarity is improved

Activity

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions