terrakube-io/terrakube

Bug description 🐞 The provider trust_signature is limited to 32 characaters. Terraform init then fails to armor-decode when verifying the signature and terraform init aborts: Error: Failed to install provider Error while installing registry.example.com/myorg/coderd v0.0.22: error verifying trust signature: unexpected EOF This only affects providers whose upstream registry metadata actually populates trust_signature. In our registry, 15 of 16 mirrored providers store '' and work fine; only coder/coderd publishes a trust signature and fails to verify. Steps to reproduce Import a provider whose upstream metadata sets signing_keys.gpg_public_keys[].trust_signature — e.g. coder/coderd. GET /terraform/providers/v1/{ns}/coderd/0.0.22/download/linux/amd64 → trust_signature is 32 chars. terraform init with that provider → error verifying trust signature: unexpected EOF. Expected behavior Full trust_signature to be stored and successful terraform init. Example repository terraform {

Feature description 💡 Currently, UI shows who triggered the Job run. It would be nice to display additional information like VCS workspace UI run example Run Triggered at/by: Timestamp by USER Source: repo name Commit: Branch name [commit id] Trigger: VCS via UI using template Plan/Apply Run reason: commit id message Job type: Plan or Plan and Apply Executed on Agent: <Agent name/ Ephemeral k8 pod name/ip> VCS workspace CLI run example Run Triggered at/by: Timestamp by USER Source: CLI Trigger: CLI using template Plan/Apply Run reason: No reason Job type: Plan or Plan and Apply Executed on Agent: <Agent name/ Ephemeral k8 pod name/ip> Anything else? No response

Bug description 🐞 We are currently testing terrakube, and we use a self-hosted gitlab instance. I have configured workspaces using git ssh as the source without using the gitlab integration. The formatSshUrl function in the Terrakube UI fails to properly convert SSH URLs to HTTPS for self-hosted GitLab/GitHub/Bitbucket instances. It only handles hardcoded domains (github.com, gitlab.com, bitbucket.org), leaving the colon in SSH URLs unconverted for any other domain. Version Affected Terrakube 2.28.0 (UI component) Root Cause In the minified UI bundle, there are two similar functions: fixSshURL (correct implementation): i.replace(":", "/").replace("git@", "https://") This correctly handles any SSH URL by: First replacing : with / Then replacing git@ with https:// formatSshUrl (buggy implementation): // Only handles specific domains: i.includes("github.com") && (i = i.replace(".com:", ".com/")) i.includes("gitlab.com") && (i = i.replace(".com:", ".com/")) i.includes("bitbucket.org")

Feature description 💡 Currently, the plan and apply outputs are pretty verbose as Terraform shows all the init and resource sync. It would be great to at least split in two dropable frames, one with the init and the other can be the plan/apply. This way expanding will only show more usefull data. If it can be possible to hide even more the resource scanning inside the plan, it will improve the information being shown. By using different drop down frames, debugging can be performed if intended. Anything else? It's great that Terrakube shows all the information related to each run. It's very appreaciated at debug time, but for regular operation, we might make that information less visible.

Feature description 💡 Hello we are testing terrakube using Qumulo as S3 backend. Qumulo need as region us-east-1 but Terrakube creates header Authorization with path that indicates "auto" as region. I've modified S3Client builder from '.region(Region.of("auto"))' to '.region(Region.US_EAST_1)'. I've also added '.chunkedEncodingEnabled(false)' and '.checksumValidationEnabled(false)' in the S3Configuration builder as it seems that Qumulo doesn't support chunks. With these changes I've been able to store state on Qumulo. I was wondering if it is possible to create parameters for those two settings, better if it is possible to also add as helm variables. Thanks Bye Anything else? No response