https://github.com/puppetlabs/pltraining-rbac
https://github.com/puppetlabs/pltraining-rbac
maintenance-mode module
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/puppetlabs/pltraining-rbac
- Owner: puppetlabs
- License: apache-2.0
- Created: 2015-03-16T18:31:04.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2025-02-04T02:18:50.000Z (4 months ago)
- Last Synced: 2025-04-02T03:57:23.756Z (about 2 months ago)
- Topics: maintenance-mode, module
- Language: Ruby
- Homepage:
- Size: 56.6 KB
- Stars: 2
- Watchers: 17
- Forks: 19
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.txt
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Codeowners: CODEOWNERS
Awesome Lists containing this project
README
# PE Console RBAC APIs
Puppet Enterprise 3.7 introduced a new Role Based Access Control layer. This
enables you to manage the permissions of local users as well as those who are
created remotely, on a directory service in very granular detail.
This module exposes some of it to the Puppet DSL. Currently, it manages
users, roles, permissions, and groups.
> This module is maintained by Puppet, but we have no plans for future feature development. We will keep it working with current versions of Puppet, but new feature development will come from community contributions. It does not qualify for Puppet Support plans.
>
> [tier:maintenance-mode]
## Usage
``` Puppet
rbac_user { 'testing account':
ensure => present,
name => 'testing',
display_name => 'Just a testing account',
email => '[email protected]',
password => 'puppetlabs',
roles => [ 1,2 ],
}
rbac_role { 'Viewers':
ensure => 'present',
description => 'Viewers',
permissions => [
{
'object_type' => 'nodes',
'action' => 'view_data',
'instance' => '*'
},
{
'object_type' => 'console_page',
'action' => 'view',
'instance' => '*'
}],
}
rbac_group { 'admins':
ensure => 'present',
roles => ['Administrators'],
}
```
## Limitations
The API does not currently allow you to update existing users, other than to
revoke the account, or update the roles attached to the user. When you ensure an
`rbac_user` is absent, the record will not be removed, just marked as revoked.
For a node that is not a standalone master to manage RBAC users, its certname
must be listed in the Console node's RBAC certificate allowlist.
Contact
-------