Andrea Cavagna

I'm going to close this issue since the problem [has been documented ](https://docs.leapp.cloud/0.14.3/troubleshooting/faq/#aws-cli-or-az-cli-is-installed-but-leapp-cant-find-it-what-can-i-do)

With the latest release the problem is solved

This could be a useful feature for whoever leaves the App open, once Leapp is closed, all the named profiles associated are turned off. This could be a great addition...

We will add this to our roadmap. We have to ensure this feature with the feature of securing the credentials in the OS password manager. Thanks for reaching us!

Hello @Nuru, since we have a scriptable CLI I think that it would be a way to import data in Leapp, we just wrote an article about it: https://medium.com/leapp-cloud/how-to-quickly-automate-aws-federated-session-generation-with-leapp-cli-e5e505653001 Is...

Thanks for the feedback! as said in #264 we still have to figure out how to return the SAML assertion to Leapp if we go with the authentication outside of...

Thanks for the kind word! Nice first issue! Can be a good first issue!

This problem is not related to the M1 silicon, this is caused because the encryption of the configuration file on Leapp is based on the Machine ID. By changing your...

exactly, for security concern of someone trying to steal the configuration encrypted file, this file can only be decrypted with the machine ID of the first system in which Leapp...

Good point, absolutely a crash of the App is not the best idea, I'll add it in the next release