This repository has been archived by the owner on Apr 29, 2021. It is now read-only.
Provide option to save intermediate bash script #111
Comments
yarikoptic
pushed a commit
to neurodebian/bats
that referenced
this issue
Aug 6, 2019
Included RPM spec contrbution to build OS packages for EL7
yarikoptic
added a commit
to neurodebian/bats
that referenced
this issue
Aug 6, 2019
Bats 1.1.0 - 2018-07-08 This is the first release with new features relative to the original Bats 0.4.0. Added: * The `-r, --recursive` flag to scan directory arguments recursively for `*.bats` files (sstephenson#109) * The `contrib/rpm/bats.spec` file to build RPMs (sstephenson#111) Changed: * Travis exercises latest versions of Bash from 3.2 through 4.4 (sstephenson#116, sstephenson#117) * Error output highlights invalid command line options (sstephenson#45, sstephenson#46, sstephenson#118) * Replaced `echo` with `printf` (sstephenson#120) Fixed: * Fixed `BATS_ERROR_STATUS` getting lost when `bats_error_trap` fired multiple times under Bash 4.2.x (sstephenson#110) * Updated `bin/bats` symlink resolution, handling the case on CentOS where `/bin` is a symlink to `/usr/bin` (sstephenson#113, sstephenson#115) * tag 'v1.1.0': (198 commits) Bats 1.1.0 bats: Replace echo with printf Extract `abort()` function travis: Remove `bats -c` wrapper travis: Enable build with default Linux image Bash Add Bash version test to Travis job. Revert "Re-add Bash version check to Docker image build" Re-add Bash version check to Docker image build Move timing test to Docker run for Linux jobs Remove version check from Docker image build Bash version via build matrix instead of script loop Fix merge error. Add return code storage for Bash version loop Add Bash version output during 'docker build' Clean up Docker image tags Add default value for Bash version Cover more Bash versions with Docker BATS_ROOT: Elide options to reset shell options BATS_ROOT: Restore comment noting issue sstephenson#113 BATS_ROOT: Use `set -P`, remove `PWD` resolution ...
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be helpful to save off the intermediate bash script that could be run without having BATS installed. The use-case I'm thinking is as a system configuration check, for example. One could right tests to ensure that a given system is in the desired state. This could aid in troubleshooting, for example.
For example, in remote troubleshooting an engineer asks that a user runs the generated script on the system. The engineer knows that in order for the system to provide its intended resources, the services of foo, bar, and baz must be running. Further, the configuration of baz must point to the service endpoint of bar and foo. And iptables must be configured to allow remote access to baz and foo.
It'd make a handy quick checklist. Thanks!
The text was updated successfully, but these errors were encountered: