Closed AlienAstronaut closed 4 years ago
I'd like to also note, the service still works because the default action is to look in the working directory for a gossfile, but we'd like to be able to specify it in the future.
Not on a computer to send exact command at the moment.
Given:
goss [global options] command [command options] [arguments...]
Does the following work?
goss -g /opt/goss/goss.yml serve [serve options]
Wow, RTFM to me. Quarantine is killing my brain cells. Thank you, that's what I was doing wrong.
Lol, all good. Glad I was able to help/unblock you. :)
Describe the bug
I'm attempting to install Goss across a large environment (Mostly Redhat 7 machines) as a service using systemd. Debugging this took quite some time because Goss doesn't support distinct exit codes yet, but in my problem solving I found that Goss doesn't find the global parameter
-g --gossfile
acceptable.How To Reproduce
Execute Goss v0.3.10 with the commands noted below in "Actual Behavior"
Expected Behavior
Expected Goss to behave according to the documentation, in that the options
-g
and--gossfile
would read in the provided YAML file without issues (excluding YAML formatting or FileNotFound errors).Actual Behavior
Attempted to run base command from
/opt/goss/
as working directory, using both the-g
and--gossfile
parameters, varying the order.Environment:
Goss Version:
v0.3.10
OS Version:Red Hat Enterprise Linux Server release 7.6 (Maipo)
Uname Output:Linux ****************** 3.10.0-957.21.2.el7.x86_64 x86_64 x86_64 x86_64 GNU/Linux
Ansible Version:v2.8.0