Skip to content

fix: label api-gateway and worker remote as Orkes-only#81

Closed
nthmost-orkes wants to merge 3 commits intomainfrom
fix/orkes-only-command-labels
Closed

fix: label api-gateway and worker remote as Orkes-only#81
nthmost-orkes wants to merge 3 commits intomainfrom
fix/orkes-only-command-labels

Conversation

@nthmost-orkes
Copy link
Copy Markdown
Contributor

Summary

  • Adds ⚠️ Requires Orkes Conductor. Not available in OSS Conductor. to the api-gateway command Long text
  • Updates worker remote Long text to lead with the Orkes-only requirement (before the EXPERIMENTAL note)

User impact

An OSS user who runs conductor api-gateway --help or conductor worker remote --help gets no indication that these commands require an enterprise server. They'd try them, get a cryptic connection or 404 error, and have no idea why. Now the first thing they read is a clear restriction notice.

Fixes conductor-oss/getting-started#20

🤖 Generated with Claude Code

…oss/getting-started#19)

Standardize on hyphens (Go/POSIX CLI convention). Add get_all as an
alias for backwards compatibility.
…-oss/getting-started#3)

Print a heads-up message before the JAR download begins so users
know to expect a large download. Also surfaces the Docker alternative
for users who want a faster first-run experience.
…/getting-started#20)

OSS users who try these commands against a local server get a confusing
error with no explanation. Add a clear note in the Long help text so the
first thing they read is that Orkes Conductor is required.
@nthmost-orkes
Copy link
Copy Markdown
Contributor Author

Superceded by a clean branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Orkes-only commands (api-gateway, worker remote) appear in OSS CLI with no indication they won't work

1 participant