Role-Based Access Control with Fugue
As development manager, imagine you’re coordinating eight users. They have different kinds of access to the default account, the two-web development accounts, and the one web-staging account. The Team Conductor’s RBAC feature enables you to manage this with a single policy written in Ludwig; a new CLI command, fugue policy; and five subcommands. If you run fugue policy -h, you’ll get some useful information about the subcommands, as expected:
| FugueWriter:~/fugue-book $ fugue policy -h |
| Usage: fugue policy [OPTIONS] COMMAND [ARGS]... |
| |
| Manage role based access control policy for Fugue |
| |
| Options: |
| -h, --help Show this message and exit. |
| |
| Commands: |
| generate-secret Generate a new secret for a specific ... |
Get Scalable Cloud Ops with Fugue now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.