Enable the controller to also manage user accounts.
It should only manage fields that are not managed by the user:
username
groups
email?
The user should be informed, by email, that their account has been created.
Ideally this is done by lldap, but not sure if that is possible, if not we'll implement it into the controller.
Enable the controller to also manage user accounts.
It should only manage fields that are not managed by the user:
- username
- groups
- email?
The user should be informed, by email, that their account has been created.
Ideally this is done by lldap, but not sure if that is possible, if not we'll implement it into the controller.
Might also be an idea to have initial options.
These values will set the respective field to that value, but only when the user is created in lldap.
Might also be an idea to have initial<field> options.
These values will set the respective field to that value, but only when the user is created in lldap.
Dreaded_X
added a new dependency 2025-03-18 15:30:35 +00:00
apiVersion: lldap.huizinga.dev/v1
kind: User
metadata:
name: dreaded_x
spec:
initial:
firstName: Tim
lastName: Huizinga
displayName: Dreaded_X
email: tim@huizinga.dev
groups:
- git
I believe there are some restrictions on the name field, so might have to figure out something for that
Resource would look like this:
```
apiVersion: lldap.huizinga.dev/v1
kind: User
metadata:
name: dreaded_x
spec:
initial:
firstName: Tim
lastName: Huizinga
displayName: Dreaded_X
email: tim@huizinga.dev
groups:
- git
```
I believe there are some restrictions on the name field, so might have to figure out something for that
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Enable the controller to also manage user accounts.
It should only manage fields that are not managed by the user:
The user should be informed, by email, that their account has been created.
Ideally this is done by lldap, but not sure if that is possible, if not we'll implement it into the controller.
Might also be an idea to have initial options.
These values will set the respective field to that value, but only when the user is created in lldap.
Add UserAccountto Add User resourceResource would look like this:
I believe there are some restrictions on the name field, so might have to figure out something for that
Not really a fan of the
initialthing. Might be better to just use the webui to manage real users.Not really a fan of the
initialthing. Might be better to just use the webui to manage real users.