Skip to content

Releases: devrev/adaas-chef-cli

Chef CLI 0.1.7: Bugfixes for custom stages

30 Sep 13:28
Compare
Choose a tag to compare

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

26 Sep 10:01
Compare
Choose a tag to compare

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

20 Sep 10:37
Compare
Choose a tag to compare

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

03 Sep 11:44
Compare
Choose a tag to compare

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

27 Aug 14:14
Compare
Choose a tag to compare
Chef CLI 0.1.3 Pre-release
Pre-release

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.
    image

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

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

22 Aug 09:58
Compare
Choose a tag to compare

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

Chef CLI 0.1.1

30 Jul 15:15
Compare
Choose a tag to compare

Improvements to example-data generation

Chef CLI 0.1.0

24 Jul 10:53
Compare
Choose a tag to compare

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