Command Migration

Note that in version 1.4.0 the syntax for certain commands has changed. Check out the release notes and the description of the updated commands on this page.

In version 1.4.0 of Bacalhau, all legacy commands will be removed. Here’s a breakdown of the old commands and their new equivalents:

Old Commands

New Commands

bacalhau create

bacalhau job run

bacalhau cancel

bacalhau job stop

bacalhau list

bacalhau job list

bacalhau logs

bacalhau job logs

bacalhau get

bacalhau job get

bacalhau describe

bacalhau job describe

bacalhau id

bacalhau agent node

bacalhau validate

bacalhau job validate

For some commands there are actions required to migrate to Bacalhau v.1.4.0. In your network. In the following view these actions are specified.

Special Attention to create , validate and describe Commands

Old Command

New Command

create Command

create accepts a v1beta1 job spec.

job run accepts the current job spec.

Users must update their job specifications to align with the new job run requirements.

describe Command

describe returns a v1beta1 job spec and its corresponding state in YAML format.

job describe provides columnar data detailing various parts of the job.

Users should expect a different output format with job describe compared to describe.

validate Command

validate validates a v1beta1 job spec.

job validate validates the current job spec.

v1beta1 job specs will not be considered valid when passed to the job validate command.

Guidance for Users Not Ready for the Changes

Users who are not prepared for the changes in CLI behavior and job specification definitions are advised to remain on Bacalhau v1.3.1. This version continues to support the legacy commands and job specifications. Users can maintain their own private Bacalhau cluster using v1.3.1.

When users are ready to transition to the new CLI behavior and job specification requirements, they can upgrade to Bacalhau v1.4.

Last updated