- Newest
- Most votes
- Most comments
Hi Andrew,
We have addressed the reported issue. Now, when you restart your Dev environment, the config file should persist. Could you please try it and let us know if you encounter any further problems? Your feedback is appreciated!
Am I correct that you have the settings described in this document?
https://docs.aws.amazon.com/codecatalyst/latest/userguide/set-up-cli.html
Since we use SSO, I thought it was inevitable that the session would be cut off after a reboot.
Andrew - I think you should be able to update the devfile.yaml to include your SSO configuration - as you know, the dev environments are ephemeral and only the stuff in the devfile is persisted.
That is an interesting idea. I had'nt contemplated doing that. It looks like with a little bit of work with setting up a command and events, i could have it copy my configuration to ~/.aws/config each time it starts up.
I have however discussed this with aws recently and its a known issue, that they are working to resolve. but this is a good work aound in the mean time.
Thanks, i tested this and it works really nicely thanks. These little improvements have big impacts on useablity!
Relevant content
- asked a year ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 6 months ago
I'm using aws configure sso https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-sso.html
I expect that i'l need to reauthenticate ( aws sso login ) after the token expires, however i shoud'nt need to configure sso, each time i use it.