We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Happened to notice a bit of an inconsistency.
When creating a role, providing or omiting client_id distinguishes between realm- and client role: https://registry.terraform.io/providers/mrparkers/keycloak/latest/docs/resources/role#client_id
client_id
That works quite nice.
However when needing to reference the role to add to a service account, one needs to work with different resource types:
Those 2 only differ by the client_id attribute that's present in the latter.
This could work in the same way as roles: A single resource type, where optional client_id distinguishes between type of role.
(Admitted, probably 'nice to have' and not top prio, seeing the backlog of issues)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Happened to notice a bit of an inconsistency.
When creating a role, providing or omiting
client_id
distinguishes between realm- and client role: https://registry.terraform.io/providers/mrparkers/keycloak/latest/docs/resources/role#client_idThat works quite nice.
However when needing to reference the role to add to a service account, one needs to work with different resource types:
Those 2 only differ by the
client_id
attribute that's present in the latter.This could work in the same way as roles: A single resource type, where optional
client_id
distinguishes between type of role.(Admitted, probably 'nice to have' and not top prio, seeing the backlog of issues)
The text was updated successfully, but these errors were encountered: