Hi! I’ve been using CloudMonkey with multiple profiles and noticed a usability issue with the current set profile command.

Right now, set profile serves both to create a new profile and to switch to an existing profile:

• When creating a profile, you run:

set profile <new_profile_name>
set url <api_url>
set apikey <api_key>
set secretkey <secret_key>
[optional: set username / set domain]

• When switching between profiles, you also run:

set profile <existing_profile_name>

The problem is that if you mistype the profile name when trying to switch, CloudMonkey silently creates a new empty profile instead of switching, which can be confusing and lead to misconfiguration.

Proposal:

Add a dedicated command for switching between existing profiles — one that does not create new profiles if the name doesn’t match.
For example:

switch profile <profile_name>

or

use profile <profile_name>

This would:

• Prevent accidental creation of unwanted profiles.
• Make the intent clearer by separating profile creation from profile switching.
• Improve usability when working with multiple CloudStack connections.

The current set profile could remain for profile creation/configuration to preserve backward compatibility.