liquid-labs / liquid-labs/liq-cli

Sketch in 'liq polices audit update <path>'

Open
#166 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
0
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Overview

Operator can update the responses to an ongoing audit.

Deliverables

liq policies audits update <path>:

  • For each question (in the TSV), operator is given an option to answer.
  • For unanswered questions, the operator can: 'affirm', 'deny', 'not applicable' or 'skip'.
  • An 'affirm' gives the option to add notes.
  • Both 'deny' and 'not applicable' require explanatory notes to be added.
  • If the question is already answered, the answer, along with any notes, are displayed and the user can 'accept' or 'update'. Accepting moves on to the next question, updating drops user into the same options as if there was no answer. Note that 'skip'ping a previously answered questions has the effect of deleting the previous answer.
  • As each question is answered, a tentative log entry is generated in the standard format (see #165) with descriptions '<affirmed/denied/skipped> "" [with notes]'
  • The entire audit is displayed back to the the user with actions for each question.
  • Once verified, the final action logs are generated and processed via the signature and commits as per #165.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the liq policies audits update <path> deliverables and issue #165 for the standard log format and signature/commit flow. Define the interaction for unanswered and previously answered questions, including notes and skip behavior. Done means the full audit can be reviewed, verified, and processed with final action logs.

Written by the indexing model from the issue text.

Assessment

Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.