Repository navigation
Conversation
Orka 4.0 renames the CLI from orka3 to orka and moves its artifacts to the orka/ S3 path (OK-6390). The client calls orka through one constant. The Dockerfile picks the path from ORKA_VERSION, installs the build as orka with an orka3 symlink, and downloads the CLI for TARGETARCH instead of always amd64, which put an x86 binary in the arm64 image. Default and CI CLI version is now 4.0.0. Tracked in DI-753. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Collaborator
Author
|
HOLD, pending the OK-6390 decision (targeted Wednesday Oct 14). The |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tracked in DI-753. Orka 4.0 renames the CLI from
orka3toorka, with no alias, and moves its artifacts to theorka/S3 path (OK-6390). This integration runs the CLI binary directly for deploy, list, delete, config, and token setup.Changes
pkg/orka/client.go: all six CLI calls go through onecliBinary = "orka"constant instead of hardcoded"orka3".Dockerfile:ORKA_VERSION:orka/…/orka.tar.gzfor 4.x and later,orka3/…/orka3.tar.gzfor 3.x. Either way, it's installed as/usr/local/bin/orka, with anorka3symlink for customers' custom scripts. The same source builds images for Orka 3.6 and 4.0.linux/amd64, so thelinux/arm64image CI publishes has been shipping an x86 CLI. It now downloads the build forTARGETARCH. arm64 Linux builds exist for every 3.x version I checked (3.2.0 through 3.6.3).ORKA_VERSIONis now4.0.0(was3.1.0)..github/workflows/ci.yml:ORKA_VERSIONis now4.0.0(was3.2.0).README.mdandexamples/.env: useorka.Testing
gofmtandgo vetare clean,go build ./...succeeds, andgo test ./...passes.3.6.3artifacts foramd64andarm64. Each installs the right architecture (x86-64 and aarch64) asorka, withorka3linked to it. I didn't do a full multi-archdocker build, because Docker wasn't running locally.official/4.0.0/orka/...(currently 403).Merge and release
ORKA_VERSION. Orka 3.6 customers need images with a 3.x CLI, so either keep publishing a 3.x line (for example, a build matrix overORKA_VERSION) or document which image versions pair with which Orka version.The GitLab and Buildkite changes are in macstadium/orka-integrations#71.
🤖 Generated with Claude Code