mirror of
https://github.com/ovh/the-bastion.git
synced 2026-05-09 08:25:27 +02:00
[GH-ISSUE #359] Bulk operations on restricted "account*" plugins? #94
Labels
No labels
answered
bug
documentation
enhancement
enhancement
feature
feature
kept-open-for-info
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/the-bastion#94
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
accountAddPersonalAccesscommand. Something like passing--accountmultiple times, or having a new--accountsoption that takes a comma separated list of account namesI 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.
@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,Coption is definitely doable.I'll keep this ticket as a reminder, knowing that it would be useful for others will help me prioritize :)