Feature request: upload custom extensions/theme/dump to keycloak

[HanXHX]

Hi,

Can you provide a way to upload/push data (jar theme file / realm dump...) to keycloak + rebuild when it changes?

Something like:

resource "clevercloud_keycloak" "main" {
   name = "test123"
} 

resource "clevercloud_keycloak_import" "theme" {
  type = "theme" # provider / theme / realm_import
  instance_id = clevercloud_keycloak.main.id
  source = "path/to/file.jar"
} 

Best,

Emilien

[miton18]

It's not as easy, because using a file path as attribute prevent us to trigger a diff on Terraform.
In other words, using a new version of file.jar, does not output any diff because the filename does not changes
So, with only a filepath, we won't be able to use resources.

What I can give you is by using actions, using this PR #317, you will be able to do what you want with something like:

...
resource "clevercloud_keycloak" "kc" {
    name = "my_kc"
    ...
    lifecycle {
        action_trigger {
            events    = [after_create]
            actions = [action.clevercloud_fsbucket_upload.upload_theme]
        }
    }
}

action "clevercloud_fsbucket_upload" "upload_theme" {
    config {
        fsbucket_id = clevercloud_fsbucket.nfs.id
        file {
            local_path = "file://path/to/file.jar"
            remote_path = "/theme/www.jar"
        }
    }
}

[HanXHX]

And calculate a checksum from local_path?

Something like:

action "clevercloud_fsbucket_upload" "upload_theme" {
    config {
        fsbucket_id = clevercloud_fsbucket.nfs.id
        file {
            local_path = "file://path/to/file.jar"
            remote_path = "/theme/www.jar"
            checksum = filesha256("/path/to/file.jar")
        }
    }
}

[miton18]

Sadly, "actions" are not trigger on attribute diff, but on event, like, resource created, resource_updated, deleted...

On resource side, the only way is to have, the file path + the file hash as attributes, and you will have to update the file hash attribute in the configuration every time it's changed.

For example, on repositories to deploy an app, we take the repository url, and the sha of the commit, that's how we signal a diff