EDGAR should read Setup-String interactively

[mbfm]

Currently, running the EDGAR Setup is done by passing the Setup-String via the CLI:

./opendut-edgar setup managed $SETUP_STRING

This should be read via stdin, so the user will only enter

./opendut-edgar setup managed

Then get a printed explanation of where to retrieve this setup string from, and then they paste it into the interactive dialog.

This ensures that the Setup-String does not end up in the command-line history and provides a better user experience.

For non-interactive use, it should be possible to pipe the Setup-String into EDGAR from a file like this:

cat setup_string.txt | ./opendut-edgar setup managed

[reimarstier]

The fallback option voluntarily opens this issue again and should be rather discouraged. What about if EDGAR reads the configuration from file?

[mbfm]

Good point, I changed the issue text to read from a file instead.

[mbfm]

Implemented in f79e07287ce8d272ee0636a55bd5f8da928b050e.