Users often get errors when calling commands which need the authentication repository because they invoked them outside of the authentication repository. By default, auth repo path is set to the current working directory. Although this location can be set by using the --path parameter, most users rarely use it and prefer to invoke the command from the correct location. These errors can look like:
taf.exceptions.ValidationFailedError: Validation of repository failed due to error: Cannot clone tmpfv5f0916/auth_repo from any of the following URLs: ['.../library/cityofsanmateo']
In order to enhance the tool's usability, the following should be done:
[ ] Try to find the authentication repository based on the current working directory.
[ ] when inside the directory which contains just one auth repository, return the location of that auth repo
[ ] if inside the auth repo, say, auth/targets, return that repository's root
[ ] if that cannot be done, raise a nice error message, saying that the auth repository could not be located
The second issue is related to key management, since the users constantly have to specify keystore location.
[ ] Add a command for initializing a .taf directory inside a directory of choice (this should be the library root). Inside that directory, create config.toml (can be empty for now) and a keystore directory. Optionally generate new keys
[ ] If the library root of the current authentication repository contains this .taf/keystore directory, read the keystore files from there. Keep the option to specify a different location.
Extend with all other tasks related to usability...
Users often get errors when calling commands which need the authentication repository because they invoked them outside of the authentication repository. By default, auth repo path is set to the current working directory. Although this location can be set by using the
--pathparameter, most users rarely use it and prefer to invoke the command from the correct location. These errors can look like:In order to enhance the tool's usability, the following should be done:
auth/targets, return that repository's rootThe second issue is related to key management, since the users constantly have to specify keystore location.
.tafdirectory inside a directory of choice (this should be the library root). Inside that directory, createconfig.toml(can be empty for now) and a keystore directory. Optionally generate new keys.taf/keystoredirectory, read the keystore files from there. Keep the option to specify a different location.Extend with all other tasks related to usability...