[GH-ISSUE #359] Bulk operations on restricted "account*" plugins? #94

Open
opened 2026-05-07 00:18:46 +02:00 by BreizhHardware · 1 comment

Originally created by @ldelelis on GitHub (Feb 10, 2023).
Original GitHub issue: https://github.com/ovh/the-bastion/issues/359

A frequent use case on our bastion implementation is to operate on multiple users to update a particular ACL. The way we do it is via looping from a regular shell, accessing a bastion admin user, and updating this ACL with the respective bastion plugin.

I'd like to know if it would be possible to implement a way to bulk these operations into a single accountAddPersonalAccess command. Something like passing --account multiple times, or having a new --accounts option that takes a comma separated list of account names

I understand this is normally an use case for Bastion groups. However, our topology requires that we use individual users for this, so groups are not an option.

Originally created by @ldelelis on GitHub (Feb 10, 2023). Original GitHub issue: https://github.com/ovh/the-bastion/issues/359 A frequent use case on our bastion implementation is to operate on multiple users to update a particular ACL. The way we do it is via looping from a regular shell, accessing a bastion admin user, and updating this ACL with the respective bastion plugin. I'd like to know if it would be possible to implement a way to bulk these operations into a single `accountAddPersonalAccess` command. Something like passing `--account` multiple times, or having a new `--accounts` option that takes a comma separated list of account names I understand this is normally an use case for Bastion groups. However, our topology requires that we use individual users for this, so groups are not an option.
Author
Owner

@speed47 commented on GitHub (Feb 15, 2023):

Hello,

This is also a use case we have from time to time, and the --account A,B,C option is definitely doable.
I'll keep this ticket as a reminder, knowing that it would be useful for others will help me prioritize :)

<!-- gh-comment-id:1431553600 --> @speed47 commented on GitHub (Feb 15, 2023): Hello, This is also a use case we have from time to time, and the `--account A,B,C` option is definitely doable. I'll keep this ticket as a reminder, knowing that it would be useful for others will help me prioritize :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/the-bastion#94
No description provided.