allow for mapping roles to users and service accounts about terraform-provider-keycloak HOT 8 CLOSED

As the #247 is closed now and #315 is merged, is this resolved now?

from terraform-provider-keycloak.

Hi @dimsedane, thanks for wanting to contribute! Feel free to post any questions you may have here along the way, I'll be happy to help.

I had initially considered a more generic keycloak_user data source as well, but my concern with using that for service accounts is that we would be relying on that naming convention which isn't guaranteed to remain consistent. I think ultimately there will be a generic keycloak_user data source regardless, and I suppose there would be nothing stopping people from using it that way, but I would probably still add a keycloak_service_account_user data source just for the extra safety.

from terraform-provider-keycloak.

Totally makes sense, I like the simplicity 👍

from terraform-provider-keycloak.

LGTM!

from terraform-provider-keycloak.

I am looking into this a little as my first try with go and Terraform development since we need it for at project.

While my need is also for a service account, would it be better for the datasource to be for a generic keycloak user, not just a service account? You could still get the service account user from the naming convention, but it would be possible to apply it broader.

from terraform-provider-keycloak.

Thank for the idea @mrparkers.

Would it better for the resource "keycloak_openid_client" to output an attribute service_account_user_id if service_accounts_enabled is set to true?

from terraform-provider-keycloak.

Any chance to get this going? We would need this.

from terraform-provider-keycloak.

Looks like this is being worked on in #247

from terraform-provider-keycloak.