heavy_script

Bugfix:

• Sudo Path Management
  • Renamed ensure_symlink to ensure_sudoers and modified its functionality to append $HOME/bin to the sudoer's PATH. This change aligns with Dragonfish's new policy restrictions, ensuring users invoking sudo have the correct path visibility.

Bugfix:

• PVC

• • Use kubectl commands to find paths rather that searching zfs

• Database Dumps

• • Fix Failed messages
• • Fix "Resource not found"

• Lifecycle

• • Include deploying applications in stop menu

[Bugfix]

• Silence error when no CNPG apps are found
• Wait for primary Postgres pod to come up prior to attempting dump
• Do not return from the database dump function after a single app failure

[Improvements]

• Add better error messages for failed database dumps (still needs some work)

[Bugfix]

• Correct command for pulling CNPG apps for database checks during backups
• Follow redirects for repo

[Features]

• Update-Only Flag: Introduced -u, --update-only flag that allows updating only specified applications. Users can provide a comma-separated list of apps or use the flag multiple times. Example usage:
• • heavyscript update -u sonarr,radarr,nextcloud
• Enhanced DNS Function: The DNS function now accepts app names, returning results only for those specified apps. Example usage:
• • heavyscript dns sonarr radarr nextcloud.

[Improvements]

• Enhanced Ignore Flag: The -i, --ignore flag now accepts comma-separated lists.
• • Example: heavyscript update --ignore sonarr,radarr,nextcloud. The previous method of using individual -i flags per app remains functional.

[Removed]

• DNS Function Changes: Removed the -a or --all flag, which is now the default for the DNS function.

[Bugfix]

• v2.8.0 broke self update, this PR reverts the change.

[Instructions]
Users already on v2.8.0 will have to do the following:

1. Open a shell
2. Enter the Heavyscript menu:

• • heavyscript
    or
• • Go to where heavyscript is installed and run:
• • bash heavy_script/heavy_script.sh

4. Choose option 4: Heavyscript Options
5. Choose option 1: Self Update

[Features]

• Add logs to update failures
• • Full logs for --verbose
• • Logs limited to 500 characters for non-verbose

[Improvements]

• Attempt fix towards updates reporting they failed, when they have not

• • Specifically handle middlewared timeouts, which is usually the cause of these false reports

• Print better error messages for updating, such as:

• • If the command itself times out, say so, and recommend a higher --timeout
• • If middlewared consistently times out, recommend a lower number of concurrent updates
• • If snapshots preventing updates are not being deleted, state that
• • Otherwise print out an error for the user

• If the update command returns that there is no update available, report that as a successful update

[Other]

• Remove restart container logic after updating container images
• Do not self update if -h or --help is called, in any context.
• Change "Removed Docker Images" to just "Removed Images".

[Notes]

• If you set a ridiculous timeout, such as 99999, then you may have to wait that long if middlewared does not have internal timeouts for its update functions. Do NOT report these as errors to me.

[Improvements]

• Improve documentation, add a note for -x stating that it is NOT a recommended flag when updating
• Improve Velero error message when namespace cannot be set

[Bugfixes]

• Set velero config settings when calling velero function
• Add additional checks for operators, do not attempt to stop them

[Bugfix]

• Handle new chart metadata for lifecycle operations
• Show skipped version for ignored applications

[Notes]
The latest version of TrueNAS SCALE introduced new chart metadata that had to be taken into account for lifecycle operations.
If you are not on SCALE version 23.10.1, checkout an earlier tag of heavyscript, and disable auto updates until you are on or beyond 23.10.1
Ex: git checkout tags/v2.7.5

[Bugfix]

• Remove helm replica set

[Bugfix]

• Set replicas when scaling with helm
• Remove outdated code for official application lifecylce
• Add additional checks in start_app function

[Bugfix]

• Fix start_app.sh and stop_app.sh scripts to handle failure cases properly

[Bugfix]

• During database dumps, use the CNPG pod with the label: ‘role: primary’, rather than assuming it will be 1.

[Features]

• Velero CLI install/update script in menu
• • Open Menu heavyscript -> 3) Backup Options -> 4) Install/Update Velero
• • This is in preparation for Truecharts velero implementation
• Update deploy.sh to better allow for installation into non-root users directories
• Default to 500 lines for pod log function
• Add disable options for all enable features, closes #132
• Ability to move back one time in some parts of the menu

[Improvements]

• Update Readme to show two different methods of running the one-liner script, (privileged/unprivileged)
• Update Readme to explain cron job paths
• Print cron path out when installing HeavyScript with one liner

[Improvement]

• Start the application if the StopAll checkbox is ticked, but the application is active, essentially resolving the conflict for the user.
• • This should solve any lingering issues with applications stopping after updating..

[Improvement]

• Fix potentially harmful message in the event a CNPG application fails to pass post-processing

[Hotfix]

• Check for script dir in /root (v2.6.1)
• Ensure HS dir for sudo user (v2.6.2)

[Features]

• Allow one-liner-scipt install for non-root users closes #118 #94
• Asks users to run certain root-requiring functions as root/sudo
• Create symbolic link in /usr/local/bin for heavyscript wrapper, for the sudo environment

[Notes]
We have removed the patches function along with its corresponding menu option. This change comes in response to iXsystems discontinuing support for all HeavyScript users, irrespective of their use case. It appears that any issues raised on systems with HeavyScript installed are being closed by iXsystems, citing "HeavyScript modifies core files" as the reason.

We suspect that the discontinuation of support might be due to the patches function, which was operative only on a specific version of TrueNAS SCALE. This function was designed to implement a patch that was scheduled to be included in the subsequent release of TrueNAS SCALE. It's important to note that HeavyScript included a version check to ensure the patches function would only run on the EXACT version it was intended for.

The specific version of TrueNAS SCALE, 22.12.0, was released nearly a year ago. Given that HeavyScript had a built-in check to prevent the patches function from running on any other version, it is perplexing why iXsystems has only now chosen to withdraw support, especially when this functionality has been irrelevant for almost a year.

[Hotfix]

• Check for script dir in /root

[Features]

• Allow one-liner-scipt install for non-root users closes #118 #94
• Asks users to run certain root-requiring functions as root/sudo
• Create symbolic link in /usr/local/bin for heavyscript wrapper, for the sudo environment

[Notes]
We have removed the patches function along with its corresponding menu option. This change comes in response to iXsystems discontinuing support for all HeavyScript users, irrespective of their use case. It appears that any issues raised on systems with HeavyScript installed are being closed by iXsystems, citing "HeavyScript modifies core files" as the reason.

We suspect that the discontinuation of support might be due to the patches function, which was operative only on a specific version of TrueNAS SCALE. This function was designed to implement a patch that was scheduled to be included in the subsequent release of TrueNAS SCALE. It's important to note that HeavyScript included a version check to ensure the patches function would only run on the EXACT version it was intended for.

The specific version of TrueNAS SCALE, 22.12.0, was released nearly a year ago. Given that HeavyScript had a built-in check to prevent the patches function from running on any other version, it is perplexing why iXsystems has only now chosen to withdraw support, especially when this functionality has been irrelevant for almost a year.

[Features]

• Allow one-liner-scipt install for non-root users closes #118 #94
• Asks users to run certain root-requiring functions as root/sudo
• Create symbolic link in /usr/local/bin for heavyscript wrapper, for the sudo environment

[Notes]
We have removed the patches function along with its corresponding menu option. This change comes in response to iXsystems discontinuing support for all HeavyScript users, irrespective of their use case. It appears that any issues raised on systems with HeavyScript installed are being closed by iXsystems, citing "HeavyScript modifies core files" as the reason.

We suspect that the discontinuation of support might be due to the patches function, which was operative only on a specific version of TrueNAS SCALE. This function was designed to implement a patch that was scheduled to be included in the subsequent release of TrueNAS SCALE. It's important to note that HeavyScript included a version check to ensure the patches function would only run on the EXACT version it was intended for.

The specific version of TrueNAS SCALE, 22.12.0, was released nearly a year ago. Given that HeavyScript had a built-in check to prevent the patches function from running on any other version, it is perplexing why iXsystems has only now chosen to withdraw support, especially when this functionality has been irrelevant for almost a year.