huawei-cloud-oa-risk-inspection

Huawei Cloud OA Service Risk Inspection

Overview

Fetch tenant resource inspection results from the Huawei Cloud Optimization Advisor (OA), Config and SecMaster services, and generate an inspection analysis report.

Workflow

Copy the following checklist and track progress:

- [ ] Step 1: Environment check
- [ ] Step 2: Fetch OA risk inspection results
- [ ] Step 3: Fetch Config resource compliance results
- [ ] Step 4: Fetch SecMaster baseline check results
- [ ] Step 5: Convert raw results
- [ ] Step 6: Generate report
- [ ] Step 7: Clean up temporary files
- [ ] Step 8: Workflow summary

Step 1: Environment check

• MUST Check whether the Python programming language is installed
• MUST Check the Python third-party library dependencies, refer to requirements.txt
  • Refer to the command pip install --dry-run -r requirements.txt
  • Expect all packages to output Requirement already satisfied
  • IF Would install appears, install the third-party library dependencies listed in requirements.txt
• MUST Check whether the hcloud command-line tool is installed
• MUST Check whether the hcloud command-line tool has authentication information configured
• If any check fails, MUST report the missing items and fix guidance to the user, and terminate the workflow

Step 2: Fetch OA risk inspection results

Call the oa_risk_inspection.py script to fetch raw risk inspection results from the Optimization Advisor (OA), with the following requirements:

• Run oa_risk_inspection.py with --help to view its help manual
• Use the question tool to ask the user how to configure the command-line parameters for running oa_risk_inspection.py
  • MUST List the command-line parameter details, including: parameter name, required/optional, default value, parameter description, etc.
  • MUST Have the user provide the necessary command-line parameter values, otherwise the script cannot run
  • MUST Ask the user to confirm the parameter values for this step's script. MUST NOT reuse or carry over answers from previous steps without explicit user confirmation for this step