ZuloOne
English
CabinetAccount
Sign in
Menu

Create a CI credential

Updated

A credential lets a pipeline upload .zulopkg files and manage Test and Development through Lifecycle Portal. It acts as the person who created it, inside the scopes you tick. It cannot mark a package Ready for production.

Note

Owners and Release managers create credentials. The hint on the form: No scope can mark a package Ready for production. That stays a person's act. A secret, if you choose one, is shown once.

The portal is lcp.getzulo.com. Its buttons are in English.

Used from:

  • GitHub Actions — no secret: the workflow signs in with its own token, for the repository and branch you trust.
  • Any other CI — a client secret, shown once, for your CI's secret store.

Scopes (tick what the job needs):

  • packages:write — upload packages to the library
  • environments:read — read environments and jobs
  • environments:write — deploy, redeploy and delete Test and Development
  • releases:write — install packages on Test and Development
  • releases:production — start a release to Production of a package already marked Ready

How to#

To create a credential, sign in at lcp.getzulo.com as an Owner or Release manager. Open CI credentials.

Under New credential, fill Name. Tick Scopes. Choose GitHub Actions or Any other CI. Press Create credential.

If you chose GitHub Actions, copy the client-id into the workflow. There is nothing to store. Under the credential, fill owner/repository and the ref (default refs/heads/main), then Trust this GitHub repository.

If you chose any other CI, copy the Client secret now. Zulo keeps only its hash. Put it in the CI secret store.

To stop a credential, press Revoke. If it has both a GitHub trust and a secret, Remove the secret when only GitHub uses it.

Example

  • Name GitHub release job
  • Scopes packages:write, releases:write
  • Used from GitHub Actions

Create credential. Trust acme/models @ refs/heads/main. The job uploads and installs on Test. A person still presses Mark Ready for production.

Tip

Do not tick releases:production unless a person already marked the package Ready and you really want the pipeline to press Release. Most tenants leave that to a Release manager in the portal.

If the command refuses#

What you see What to do
Credentials are managed by the owners and release managers Sign in as one of those roles, or ask them.
The secret box is gone after a reload It is shown once. Create a new credential if you did not copy it.
Revoke already done The row stays, marked revoked. It cannot sign in again.

See also

Was this page helpful?