Comment 2 for bug 1505504
Revision history for this message
| Richard Harding (rharding) wrote Re: error when destroying current environment in a multi-environment scenario | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Defaulting to admin seems like it might not be best as our goal is to not have folks interact with that environment. I wonder if it'd be best to either have some sort of 'no current environment selected' state or if it should be historically based?
Thinking that through, if it's historically based you'd still run into the same issue. If I go in and destroy many of the environments in there I'd end up not having a good fallback to go to.