If group name contains "key" in it, it is truncated in output about the-bastion HOT 3 CLOSED

Nice catch, you're right key is a reserved prefix, I'll add a pre-check to groupCreate to ensure such group can't be created.
As you probably saw, all the bastion group names (actually, bastion group roles) are mapped to OS groups, using the "key" prefix (and some suffixes for the roles).

Removing this constraint can be done, but it needs thorough testing, to ensure there's no confusion between "a bastion group name" and "a system group mapped to a bastion group" anywhere in the code. So I'll start by just denying the creation of such groups, and lifting this limitation only when I'm sure there are no longer any side effect of prepending a group name with key.

from the-bastion.

It seems that it's tied to this as a reserved keyword key for groupName (and accountName it seems).
We'll consider to rename our group so, but maybe a warning should come up when such a group with reserved prefix is created

Moreover, in your regex /^key/, what happen if somebody creates a keykeylogy group?

Thanks anyway.

Edit: Missed copy/paste.

from the-bastion.

Closing this issue, and opening another one (without the "bug" tag) for the future feature of supporting groups names starting with "key"

from the-bastion.