Chef CLI 0.2.0

Two new capabilites are added:

ctx switch

to easily switch into the context of a sync unit without needing to manually copy various environment variables:

$ export DEVREV_TOKEN=$(devrev profiles get-token access)
$ chef-cli ctx switch --env dev
9537fba4-87e5-47eb-b66c-c5315385cb25: jira / Some Test Project
f513e555-d6c7-45e5-a35f-af084e0e88a6: jira / Other Test Project
$ eval $(chef-cli ctx switch --env dev --id 9537fba4-87e5-47eb-b66c-c5315385cb25)

chef-cli ctx switch queries our backend for the list of airdrop syncs, and prints it. When the --id is provided, the context of the sync unit is emitted to environment variable (as a bash command that can be evaled)

Error reporting on 'try transformation'

When trying out a transformation, the jq errors that are found are reported per-field, together with any mismatches in between the format of the output an what DevRev expects. This helps to quickly iterate 'use jq expression' transformations:

Chef CLI 0.1.7: Bugfixes for custom stages

The previous releases had issues when mapping to custom stages in case:

• no starting_stage is provided in the metadata
• custom statuses are provided
  These are now fixed

Chef CLI 0.1.6: low-code inspection command

Adds a helpful command

chef-cli low-code --env prod > low_code.json

That allows extracting the low-code mappings that are driving the in-app mapping screen for inspection and bug reporting.

Chef CLI 0.1.5: New Initial mapping system

The main focus of this release is a new system of managing initial domain mappings.

Instead of promoting a single blueprint as the initial domain mapping of the org, there is now a separate screen for reviewing the current initial domain mappings, and the blueprint of the latest test import can be 'merged' into it, enabling:

• multiple possible targets, with the end-user deciding in the main DevRev UI how to map. For example it is now possible to encode a mapping like '"task" in the external system may map to issue or ticket in devrev'
• mappings applying to record type categories

Two new transformation methods are added:

• Mapping to custom stages
• Mapping permissions

Some features that don't have good E2E support in airdrop are removed:

• Mapping to custom objects
• Selecting a existing devrev record for anything but parts

Some bugs are fixed:

• The behavior when changing a fields mapping to "use devrev record" requires editing the default id filled in is made less confusing by not filling in a full default id.

Chef CLI 0.1.4

Adds the ability to override the 'manage' UIs port on localhost with a -p flag.
Changes the default port to 13333

Chef CLI 0.1.3

A -m flag is added to the manage command, allowing a local file to be provided as metadata, for example:
chef-cli manage --end dev -m metadata.json,
this enables to use:

• raw jq transformations using an external field as input.
  

• filling in example input data by click of a button for trying out the transformation.
  

In this case it is not validated that the local file is the same as the one submitted by the snapin, this has to be ensured by the user.

Chef CLI 0.1.2

Fixes a bug impacting the 'choose a fixed {object} from devrev' transformation, if the target field is an array.

Chef CLI 0.1.1

Improvements to example-data generation

Chef CLI 0.1.0

Initial release of the chef-cli tool for ADaaS recipe development.