Orthevs Orthevs Fathom new horizons
Menu

Workshop wiki · German and English

Json CLI Jq Fallback

This example is a controlled shell scripting lab. It is safe for local execution and uses generated data only.

Content language · German and EnglishSize · 31.1 KBexamples/15-json-cli-jq-fallback/README.md
Workshop examples as ZIP files
Learning progress in the web app

Mark chapters as read, view reading progress and check off practice modules after enabling the optional web app. Workshop progress is calculated from chapters across all document pages. Your choices stay on this device; there is no account or server sync. Installation is not required. Withdrawing your choice in Privacy settings deletes the progress.

Reading progress0%
0%
0 / 6 chapters read
Other language versionGreek ↗

Json CLI Jq Fallback

Focus: JSON-Input, jq-Integration und Fallback-Parser.

Purpose

This example is a controlled shell scripting lab. It is safe for local execution and uses generated data only.

01 / 06

Documentation

02 / 06

Files

03 / 06

Run

bash
./run.sh

The script writes temporary evidence below work/. The directory is ignored by Git.

04 / 06

Review Questions

    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
    1. How does this example demonstrate JSON-Input, jq-Integration und Fallback-Parser with safe Bash behavior?
05 / 06

Practice Appendix: Example Json CLI Jq Fallback

This appendix is a working backlog for longer trainings, reviews and repetitions. Each task can be checked locally with Bash, test data and a Git repository.

A001. JSON-Input, jq-Integration und Fallback-Parser

  • Task: validate input and connect the observation explicitly to JSON-Input, jq-Integration und Fallback-Parser.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A002. Bash

  • Task: explain exit code and connect the observation explicitly to Bash.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A003. Testing

  • Task: check quoting and connect the observation explicitly to Testing.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A004. Security

  • Task: test error path and connect the observation explicitly to Security.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A005. JSON-Input, jq-Integration und Fallback-Parser

  • Task: review log output and connect the observation explicitly to JSON-Input, jq-Integration und Fallback-Parser.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A006. Bash

  • Task: trace cleanup and connect the observation explicitly to Bash.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A007. Testing

  • Task: scope portability and connect the observation explicitly to Testing.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A008. Security

  • Task: mark security risk and connect the observation explicitly to Security.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A009. JSON-Input, jq-Integration und Fallback-Parser

  • Task: document recovery path and connect the observation explicitly to JSON-Input, jq-Integration und Fallback-Parser.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A010. Bash

  • Task: write review rule and connect the observation explicitly to Bash.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A011. Testing

  • Task: validate input and connect the observation explicitly to Testing.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A012. Security

  • Task: explain exit code and connect the observation explicitly to Security.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A013. JSON-Input, jq-Integration und Fallback-Parser

  • Task: check quoting and connect the observation explicitly to JSON-Input, jq-Integration und Fallback-Parser.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A014. Bash

  • Task: test error path and connect the observation explicitly to Bash.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A015. Testing

  • Task: review log output and connect the observation explicitly to Testing.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A016. Security

  • Task: trace cleanup and connect the observation explicitly to Security.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A017. JSON-Input, jq-Integration und Fallback-Parser

  • Task: scope portability and connect the observation explicitly to JSON-Input, jq-Integration und Fallback-Parser.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A018. Bash

  • Task: mark security risk and connect the observation explicitly to Bash.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A019. Testing

  • Task: document recovery path and connect the observation explicitly to Testing.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A020. Security

  • Task: write review rule and connect the observation explicitly to Security.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A021. JSON-Input, jq-Integration und Fallback-Parser

  • Task: validate input and connect the observation explicitly to JSON-Input, jq-Integration und Fallback-Parser.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A022. Bash

  • Task: explain exit code and connect the observation explicitly to Bash.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A023. Testing

  • Task: check quoting and connect the observation explicitly to Testing.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A024. Security

  • Task: test error path and connect the observation explicitly to Security.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A025. JSON-Input, jq-Integration und Fallback-Parser

  • Task: review log output and connect the observation explicitly to JSON-Input, jq-Integration und Fallback-Parser.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A026. Bash

  • Task: trace cleanup and connect the observation explicitly to Bash.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A027. Testing

  • Task: scope portability and connect the observation explicitly to Testing.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A028. Security

  • Task: mark security risk and connect the observation explicitly to Security.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A029. JSON-Input, jq-Integration und Fallback-Parser

  • Task: document recovery path and connect the observation explicitly to JSON-Input, jq-Integration und Fallback-Parser.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A030. Bash

  • Task: write review rule and connect the observation explicitly to Bash.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A031. Testing

  • Task: validate input and connect the observation explicitly to Testing.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A032. Security

  • Task: explain exit code and connect the observation explicitly to Security.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A033. JSON-Input, jq-Integration und Fallback-Parser

  • Task: check quoting and connect the observation explicitly to JSON-Input, jq-Integration und Fallback-Parser.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A034. Bash

  • Task: test error path and connect the observation explicitly to Bash.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A035. Testing

  • Task: review log output and connect the observation explicitly to Testing.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A036. Security

  • Task: trace cleanup and connect the observation explicitly to Security.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A037. JSON-Input, jq-Integration und Fallback-Parser

  • Task: scope portability and connect the observation explicitly to JSON-Input, jq-Integration und Fallback-Parser.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A038. Bash

  • Task: mark security risk and connect the observation explicitly to Bash.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A039. Testing

  • Task: document recovery path and connect the observation explicitly to Testing.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A040. Security

  • Task: write review rule and connect the observation explicitly to Security.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A041. JSON-Input, jq-Integration und Fallback-Parser

  • Task: validate input and connect the observation explicitly to JSON-Input, jq-Integration und Fallback-Parser.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A042. Bash

  • Task: explain exit code and connect the observation explicitly to Bash.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A043. Testing

  • Task: check quoting and connect the observation explicitly to Testing.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A044. Security

  • Task: test error path and connect the observation explicitly to Security.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A045. JSON-Input, jq-Integration und Fallback-Parser

  • Task: review log output and connect the observation explicitly to JSON-Input, jq-Integration und Fallback-Parser.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A046. Bash

  • Task: trace cleanup and connect the observation explicitly to Bash.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A047. Testing

  • Task: scope portability and connect the observation explicitly to Testing.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A048. Security

  • Task: mark security risk and connect the observation explicitly to Security.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A049. JSON-Input, jq-Integration und Fallback-Parser

  • Task: document recovery path and connect the observation explicitly to JSON-Input, jq-Integration und Fallback-Parser.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A050. Bash

  • Task: write review rule and connect the observation explicitly to Bash.
  • Evidence: Record the checked command, expected output, actual output and exit code.
  • Operations question: What happens with empty input, missing files, missing tools and repeated execution?
  • Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
  • Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.
06 / 06

SH · Orthevs Academy

31 modules as one continuous learning path.

The sequence remains unchanged: from the lab skeleton through technical foundations and operating models to final troubleshooting. The technical directory names are deliberately preserved.

Practice modules

Orthevs as an app

Install Orthevs

The Orthevs web app can be installed on supported mobile devices and desktop browsers.

iPhone and iPad

Open Orthevs in Safari. Tap Share, then Add to Home Screen. Enable Open as Web App if offered, then tap Add.

Android

For the web app, open the browser menu and choose Install app or Add to Home screen. Confirm the installation.

Desktop browser

Open the browser menu or the install icon in the address bar, then choose Install app or Add to Dock.

Web app installation depends on your browser. If no install prompt appears, follow the browser steps shown above.