Team command parameter consistency: --email vs --user-id

[jage]

Issue

The team commands currently use inconsistent parameter names for identifying users:

• team invite --email <string> - Uses email for inviting
• team update --user-id <string> - Uses user-id (UUID) for updating
• team remove --email <string> - Uses email for removing

Questions

1. Should we standardize on one approach?

   • Option A: Always use --email for user identification
   • Option B: Always use --user-id for user identification
   • Option C: Keep current behavior (different commands use different identifiers based on what's most natural)

2. If we standardize, which identifier is preferred?

   • Email is more user-friendly and human-readable
   • User ID (UUID) is more consistent with instance/VPC commands that use numeric IDs

Context

This was discovered during a CLI parameter consistency audit. All instance and VPC commands now consistently use --id flags instead of positional arguments.

[dentarg]

These are inconsistencies in the API too, so not easily addressed here.

[jage]

These are inconsistencies in the API too, so not easily addressed here.

Can we adress in the API? Otherwise can we work around it here (doing extra lookup to get correct value for API)?

[dentarg]

Both are possible, but we probably want to avoid extra lookups, teams can have many members. Looks like it is team update that should gain support for email, as that's the only one that works and can work for team invite. :-)