enh: support environment block on keycloack resource

[MathFrenchToast]

description

enable a environment {} block on the keycloack resource

what this wil solve

by declaring env vars inside the tf files, we avoid manipulation in the console and automate more (the whole purpose of iac)

proposal

following what exists on Docker
one could declare (e.g.):

resource "clevercloud_addon" "keycloak" {
  name                 = "keycloak-auth"
  plan                 = "base"
  region               = var.region
  third_party_provider = "keycloak"

 # proposal
  environment = {
    CC_KEYCLOAK_REALMS = "prod-realm, staging-realm"
  }
}

[miton18]

Hi @MathFrenchToast , because Keycloak is a meta product which manage underlying resources (like the java application) we don't want to configure the resources directly.

Do you want the Keycloak addon to expose CC_KEYCLOAK_REALMS to linked applications

or

Do you want to "pre create" some realms in keycloak ?

[MathFrenchToast]

hi,
As a devops guy, I want to avoid as much as possible the clever console usage to setup or maintain a resource.

When we instantiate the add-on, it creates a Java app.
The java app is customized by settings env vars
among all the "CC_KEYCLOACK" vars, some are key to the set-up, like: CC_KEYCLOAK_REALMS, CC_KEYCLOAK_HOSTNAME

My aim here is to be able to set as many values as possible,
Maybe I can do it some

side note: env vars def for Keycloak are not documented in: https://www.clever.cloud/developers/doc/reference/reference-environment-variables

[davlgd]

Keycloak is a managed service with its own API. You can define some settings at creation, some through API (and thus Terraform). As Keycloak is a Java App you can also edit its environment variables through API for example.

We discourage users to edit CC_ env vars as they're part of the product configuration, except for those documented (such as realms management, documented in Keycloak page).

We don't provide a way to edit all env vars for now, as it's not a need which was expressed by customers (until this issue), with important risks of misconfiguration. We'll discuss how to manage it and how to integrate it in the roadmap.

If you have more details about what you need to do exactly, feel free to share.

[miton18]

Keycloak configurations:

• access_domain is available
• handle https://www.clever.cloud/developers/doc/addons/keycloak/#admin-hostname
• CC_KEYCLOAK_REALMS is harder to handle, as a first step we can use the "realms" option of the api for the First Boot, and have a "use state for unknown" on this attribute (not yet available)
• for all others, we can use a environment block and use a dedicated Keycloak product API in order to validate and update application env