I'm using an authentication helper command to help us integrate the Rust Openstack clients with SSO. However in cases where the SSO authentication fails, or we need to repopulate the local SSO cache, I'd like for the client's authentication flow to fail early. Ideally if the exit code is not zero then the clients would just not proceed with the rest of the request. At the moment my authentication helper exits with code 1 but the osc command will continue until it gets a 404 against the /auth/tokens endpoint. Perhaps it would be nicer if the Openstack client quit when it got exit code !=0 from the auth-helper, and then the stderr warning messages get upgraded to error messages instead, to make it clearer what has happened?
I'm using an authentication helper command to help us integrate the Rust Openstack clients with SSO. However in cases where the SSO authentication fails, or we need to repopulate the local SSO cache, I'd like for the client's authentication flow to fail early. Ideally if the exit code is not zero then the clients would just not proceed with the rest of the request. At the moment my authentication helper exits with code 1 but the
osccommand will continue until it gets a404against the/auth/tokensendpoint. Perhaps it would be nicer if the Openstack client quit when it got exit code !=0 from the auth-helper, and then the stderr warning messages get upgraded to error messages instead, to make it clearer what has happened?