General Secret management within openDuT

Open kKdH opened this issue 6 months ago • 0 comments

The integration of VIPER introduces the requirement that users must enter certain secrets (credentials/keys/tokens) to run tests. For example, an SSH key is needed to allow openDuT to check out a Git repository containing a test suite (#360).

Therefore we have to extend openDuT to manage and store secrets of different kind.

Jun 03 '25 12:06 kKdH