Skip to content

darnit plan --profile still refuses after #597 fixed the reason #709

Closed

Description

@mlieberman85

darnit plan --profile still refuses, and the reason it gives no longer applies.

#576 made darnit audit --profile filter the controls and left plan refusing the flag, because plan crashed on frameworks whose controls carry no level (#568), so the flag couldn't be wired in a way that could be tested on the Baseline. #597 fixed that crash and closed #568.

On main (155dcc1), on jonschlinkert/is-odd:

  • darnit plan <repo> exits 0 and prints the plan.
  • darnit plan --profile level1_quick <repo> exits 1 with darnit plan does not support --profile yet (#568); use darnit audit --profile, which points at a closed issue.
  • darnit audit --profile level1_quick <repo> audits 26 of the 66 controls.

Suggested fix: narrow the plan with _resolve_profile_ids as cmd_audit does, with the same errors for an unknown profile or an empty selection, and remove the refusal and its comment in cmd_plan.


Drafted with AI assistance (Claude), reviewed and filed by me. Measurements quoted were executed and verified.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    module-coredarnit core frameworkneeds triageAwaiting maintainer review

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions