You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have run fig doctor in the affected terminal session
I have run fig restart and replicated the issue again
Operating system
Red Hat in my case, but presumably all
Expected behaviour
I would expect that before the autoinstaller runs, it would give us sufficient information about what it will do.
The idea that we should be expected to allow remote scripts to be run as root on servers we log into is incomprehensible.
First, tell us that it will run as root:
this at least gives a ballpark idea of the level of risk
it also in some cases lets us know that it's going to fail (and perhaps get us in trouble, depending on how much attention sysadmins pay to the logged info of attempts at using sudo)
Second, tell us exactly what it will install.
Actual behaviour
None of this information is given.
it doesn't tell us that one needs to be able to run arbitrary scripts as root
it doesn't tell us what it will install.
Steps to reproduce
Ensure that one's SSH config file includes the fig config to install on remote machines.
Environment
No response
The text was updated successfully, but these errors were encountered:
Checks
fig doctor
in the affected terminal sessionfig restart
and replicated the issue againOperating system
Red Hat in my case, but presumably all
Expected behaviour
I would expect that before the autoinstaller runs, it would give us sufficient information about what it will do.
The idea that we should be expected to allow remote scripts to be run as root on servers we log into is incomprehensible.
First, tell us that it will run as root:
Second, tell us exactly what it will install.
Actual behaviour
None of this information is given.
Steps to reproduce
Ensure that one's SSH config file includes the fig config to install on remote machines.
Environment
No response
The text was updated successfully, but these errors were encountered: