mrlunchbox777 / basic-setup Goto Github PK

When attempting to find the shared-scripts directory right now it hard fails. Given that this script runs as part of the rc file, a hard fail is unacceptable; it could prevent boots, opening terminals, running scripts, etc.

Contact Details

[email protected]

Feature Description

Add nmap to the managed packages

Why?

It is a very broad network discovery tool

What-should happen?

nmap should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "nmap")' resources/install/index.json should return the details for managing the nmap package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add cut to the managed packages

Why?

It allows you to remove sections of each lines from each file(s)

What-should happen?

cut should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "cut")' resources/install/index.json should return the details for managing the cut package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add uniq to the managed packages

Why?

It reports or omits repeated lines in text

What-should happen?

uniq should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "uniq")' resources/install/index.json should return the details for managing the uniq package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add traceroute to the managed packages

Why?

A network diagnostic tool for debugging

What-should happen?

traceroute should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "traceroute")' resources/install/index.json should return the details for managing the traceroute package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add history to the managed packages

Why?

It provides history expansion to review shell commands

What-should happen?

history should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "history")' resources/install/index.json should return the details for managing the history package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add strace to the managed packages

Why?

It allows you to trace system calls and signals

What-should happen?

strace should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "strace")' resources/install/index.json should return the details for managing the strace package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add sar to the managed packages

Why?

It supports a cli gui for viewing system resources

What-should happen?

sar should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "sar")' resources/install/index.json should return the details for managing the sar package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add find to the managed packages

Why?

Allows searching in filesystems

What-should happen?

find should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "find")' resources/install/index.json should return the details for managing the find package

Code of Conduct

• I agree to follow this project's Code of Conduct

Move the name property to the key of the object (array->object) to make merging in jq easier. This should also include several shared scripts that will make the name a property as well to ensure that name is available in all contexts when being used (e.g. get-package, get-packages).

Current:

    {
      "command": "aws",
      "description": "This package provides a unified command line interface to Amazon Web Services.",
      "enabled": true,
      "install-page": "https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html",
      "labels": [
        "all",
        "big-bang",
        "big-bang-full"
      ],
      "name": "AWS CLI",
      "package-managers": [
        {
          "arguments": "",
          "enabled": false,
          "manager-name": "apt-get",
          "notes": "Version 1 is available, but causes more issues than installing manually.",
          "package-name": "awscli"
        },
        {
          "arguments": "",
          "enabled": false,
          "manager-name": "brew",
          "notes": "Curling for the aws is better than brew.",
          "package-name": "awscli"
        },
        {
          "arguments": "",
          "enabled": true,
          "manager-name": "curl",
          "notes": "",
          "package-name": "awscli"
        },
        {
          "arguments": "",
          "enabled": false,
          "manager-name": "dnf",
          "notes": "Not available.",
          "package-name": ""
        },
        {
          "arguments": "",
          "enabled": false,
          "manager-name": "pacman",
          "notes": "Version 1 is available, but causes more issues than installing manually.",
          "package-name": "aws-cli"
        },
        {
          "arguments": "",
          "enabled": true,
          "manager-name": "winget",
          "notes": "",
          "package-name": "Amazon.AWSCLI"
        }
      ],
      "pinned-version": null
    },

New:

    "AWS CLI": {
      "command": "aws",
      "description": "This package provides a unified command line interface to Amazon Web Services.",
      "enabled": true,
      "install-page": "https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html",
      "labels": [
        "all",
        "big-bang",
        "big-bang-full"
      ],
      "package-managers": [
        {
          "arguments": "",
          "enabled": false,
          "manager-name": "apt-get",
          "notes": "Version 1 is available, but causes more issues than installing manually.",
          "package-name": "awscli"
        },
        {
          "arguments": "",
          "enabled": false,
          "manager-name": "brew",
          "notes": "Curling for the aws is better than brew.",
          "package-name": "awscli"
        },
        {
          "arguments": "",
          "enabled": true,
          "manager-name": "curl",
          "notes": "",
          "package-name": "awscli"
        },
        {
          "arguments": "",
          "enabled": false,
          "manager-name": "dnf",
          "notes": "Not available.",
          "package-name": ""
        },
        {
          "arguments": "",
          "enabled": false,
          "manager-name": "pacman",
          "notes": "Version 1 is available, but causes more issues than installing manually.",
          "package-name": "aws-cli"
        },
        {
          "arguments": "",
          "enabled": true,
          "manager-name": "winget",
          "notes": "",
          "package-name": "Amazon.AWSCLI"
        }
      ],
      "pinned-version": null
    },

In memory when in use will look like current, i.e. get package. The list of packages will include the name property and name key, i.e. get packages. The reason for not storing both is to ensure that there is only one source of truth.

Contact Details

[email protected]

Feature Description

Add iostat to the managed packages

Why?

It supports a cli gui for viewing system devices i/o transfer rates

What-should happen?

iostat should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "iostat")' resources/install/index.json should return the details for managing the iostat package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add kill to the managed packages

Why?

It can terminate processes

What-should happen?

kill should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "kill")' resources/install/index.json should return the details for managing the kill package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add uname to the managed packages

Why?

It prints system information

What-should happen?

uname should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "uname")' resources/install/index.json should return the details for managing the uname package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add tcpdump to the managed packages

Why?

It is a packet analyzer for networking management

What-should happen?

tcpdump should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "tcpdump")' resources/install/index.json should return the details for managing the tcpdump package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add ps to the managed packages

Why?

It shows a snapshot of the current processes

What-should happen?

ps should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "ps")' resources/install/index.json should return the details for managing the ps package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add cat to the managed packages

Why?

It concatenates and prints files

What-should happen?

cat should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "cat")' resources/install/index.json should return the details for managing the cat package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Chore Description

Update LICENSE and .github/LICENSE, specifically the year

Steps to Test

1. Read the year in the license

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add airmon-ng to the managed packages

Why?

It supports monitoring and diagnosing wireless network devices

What-should happen?

airmon-ng should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "airmon-ng")' resources/install/index.json should return the details for managing the airmon-ng package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add df to the managed packages

Why?

It gets filesystem disk usage

What-should happen?

df should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "df")' resources/install/index.json should return the details for managing the df package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add dig to the managed packages

Why?

It is a cli for interfacing with dns servers and is helpful for debugging

What-should happen?

dig should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "dig")' resources/install/index.json should return the details for managing the dig package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add vmstat to the managed packages

Why?

It supports a cli gui for viewing vm resources

What-should happen?

vmstat should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "vmstat")' resources/install/index.json should return the details for managing the vmstat package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add wget to the managed packages

Why?

It provides a non-interactive network downloader

What-should happen?

wget should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "wget")' resources/install/index.json should return the details for managing the wget package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add tr to the managed packages

Why?

It can translate/remove characters from a stream

What-should happen?

tr should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "tr")' resources/install/index.json should return the details for managing the tr package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add stap to the managed packages

Why?

It provides a frontend for interacting with the systemtap tool for probing

What-should happen?

stap should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "stap")' resources/install/index.json should return the details for managing the stap package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add sort to the managed packages

Why?

It sorts lines of text

What-should happen?

sort should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "sort")' resources/install/index.json should return the details for managing the sort package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add head to the managed packages

Why?

It can output the first part of files

What-should happen?

head should be a package in the index.json

when supporting on mac you need ghead

Steps to Test

1. jq '.packages[] | select(.name = "head")' resources/install/index.json should return the details for managing the head package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add bat to the managed packages

Why?

It's cat, but with paging like less, formatting, language interpretation, syntax highlighting, and pretty printing

What-should happen?

bat should be a package in the index.json

Steps to Test

jq '.packages[] | select(.name = "nmon")' resources/install/index.json should return the details for managing the nmon package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add airodump-ng to the managed packages

Why?

It supports wireless packet capture

What-should happen?

airodump-ng should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "airodump-ng")' resources/install/index.json should return the details for managing the airodump-ng package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add [nl] to the managed packages

Why?

It adds line numbering to files/stdin and prints them

What-should happen?

nl should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "nl")' resources/install/index.json should return the details for managing the nl package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add nmon to the managed packages

Why?

It supports a cli gui for viewing system resources

What-should happen?

nmon should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "nmon")' resources/install/index.json should return the details for managing the nmon package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add iptables to the managed packages

Why?

It is an administration tool for packet filtering and NAT

What-should happen?

iptables should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "iptables")' resources/install/index.json should return the details for managing the iptables package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add sed to the managed packages

Why?

Useful for streaming and processing text, particularly in piping cli output

What-should happen?

sed should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "sed")' resources/install/index.json should return the details for managing the sed package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add netstat to the managed packages

Why?

It supports a cli for querying local machine network resources

What-should happen?

netstat should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "netstat")' resources/install/index.json should return the details for managing the netstat package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add echo to the managed packages

Why?

It prints a line of text

What-should happen?

echo should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "echo")' resources/install/index.json should return the details for managing the echo package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add top to the managed packages

Why?

Displays running tasks and information about them

What-should happen?

top should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "top")' resources/install/index.json should return the details for managing the top package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add htop to the managed packages

Why?

It provides an interactive cli gui for running processes

What-should happen?

htop should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "htop")' resources/install/index.json should return the details for managing the htop package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add less to the managed packages

Why?

It reads and allows scrolling and viewing of files section at a time (better than more)

What-should happen?

less should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "less")' resources/install/index.json should return the details for managing the less package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add grep to the managed packages

Why?

It prints lines from a source that match a pattern

What-should happen?

grep should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "grep")' resources/install/index.json should return the details for managing the grep package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add curl to the managed packages

Why?

Supports data transfer over a number of protocols

What-should happen?

curl should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "curl")' resources/install/index.json should return the details for managing the curl package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add fmt to the managed packages

Why?

It formats text uniformly and then prints it

What-should happen?

fmt should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "fmt")' resources/install/index.json should return the details for managing the fmt package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add lsof to the managed packages

Why?

It lists open files and information about them

What-should happen?

lsof should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "lsof")' resources/install/index.json should return the details for managing the lsof package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add ping to the managed packages

Why?

It is a basic, but deep, network connectivity investigation tool

What-should happen?

ping should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "ping")' resources/install/index.json should return the details for managing the ping package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add dtrace to the managed packages

Why?

It allows you to create static probes

What-should happen?

dtrace should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "dtrace")' resources/install/index.json should return the details for managing the dtrace package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add tail to the managed packages

Why?

It can output the last part of files

What-should happen?

tail should be a managed package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "tail")' resources/install/index.json should return the details for managing the tail package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add awk to the managed packages

Why?

Adds a fully featured pattern scanning and processing language that is also very helpful for cli piping

What-should happen?

awk should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "awk")' resources/install/index.json should return the details for managing the awk package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add ssh to the managed packages

Why?

It is the default OpenSSH client, it enables remote shells

What-should happen?

ssh should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "ssh")' resources/install/index.json should return the details for managing the ssh package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add atop to the managed packages

Why?

It provides a cli gui for interacting with system resources and running processes

What-should happen?

atop should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "atop")' resources/install/index.json should return the details for managing the atop package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

What happened?

error running environment-validation -c -l "core"

add the dev-sso to the help notes (helm-install)

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

Feature Description

Add mtr to the managed packages

Why?

It is broad network diagnostic tool

What-should happen?

mtr should be a package in the index.json

Steps to Test

1. jq '.packages[] | select(.name = "mtr")' resources/install/index.json should return the details for managing the mtr package

Code of Conduct

• I agree to follow this project's Code of Conduct

Contact Details

[email protected]

What-should happen?

Support DNF xclip, this will require allowing chained dependencies in the install/index.json

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct