Skip to content

docs(readme): use the staging environment in the ssh --env example - #164

Open
mlilien wants to merge 1 commit into
omnect:mainfrom
mlilien:docs/readme-staging-env
Open

mlilien wants to merge 1 commit into
omnect:mainfrom
mlilien:docs/readme-staging-env

Conversation

@mlilien

@mlilien mlilien commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

Summary

  • The --env example for ssh set-connection now uses the staging environment: backend https://cp.staging.omnect.conplement.cloud, Keycloak https://keycloak.staging.omnect.conplement.cloud, realm cp-stag. The device and file names in the example and in the docker example are renamed from dev_* to staging_*.
  • Bump the version to 0.29.3.

Reason

The dev environment was removed, together with its backend and its Keycloak realm cp-dev. A user who copied the example got a configuration that does not work. Staging is now the only environment besides the default prod. Staging has its own Keycloak instance, so the provider URL changes too. The cp-cli client exists in realm cp-stag and accepts the http://localhost:4000 redirect.

The dev environment and its Keycloak realm no longer exist. The example
now uses the staging backend, its Keycloak instance and realm cp-stag.
Bump the version to 0.29.3.

Signed-off-by: Marcel Lilienthal <134974+mlilien@users.noreply.github.com>
@mlilien
mlilien requested a review from JanZachmann November 20, 2026 16:06
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.

2 participants