terraform-provider-keycloak
terraform-provider-keycloak copied to clipboard
mrparkers
Terraform provider for Keycloak
Hi, I have a sandbox environment that allows a mix of clients managed by terraform and some manually provisioned resources. Occasionally, a client managed by Terraform gets deleted accidentally. Typically,...
Closes #734 Adds two optional attributes to the LDAP user attribute mapper: `attribute_default_value` and `is_binary_attribute`
The LDAP user attribute mapper default value field is missing. In the API config map, this corresponds to the `attribute.default.value` key and adding it would allow for setting a default...
Hi, my team and i are managing a very large Keycloak realm using your provider. Many teams are involved in our whole setup. The basic workflow is like this: -...
related to issue #731 When trying to modify a keycloak created existing openid_user_client_role_protocol_mapper you get the following error. │ Error: validation error: a protocol mapper with name client roles already...
Currently, the resource "keycloak_openid_client_scope" allows you to create new resources and returns the client_scope_id However, if you are working on either keycloak_openid_user_client_role_protocol_mapper or keycloak_openid_user_attribute_protocol_mapper for any of the built-in client...
This pull requests resolve the issue https://github.com/mrparkers/terraform-provider-keycloak/issues/729. The property `default_mappers` was added to the `keycloak_ldap_user_federation` indicating whether the default mappers should be created or not. The default is true. Closes...
The `keycloak_ldap_user_federation` resource creates several default mappers. These default mappers are not manageable by terraform. Therefore, an additional flag on the `keycloak_ldap_user_federation` resource to delete all default mappers would be...
We are trying to upgrade from version = "= 2.0.0" to 3.10.0. Noticed that this is a breaking change. Is it safe to apply? I tried to remove the resource...
