Skip to content

Releases: rockcarver/frodo-cli

Frodo CLI 4.0.0-12

27 Feb 17:55

Choose a tag to compare

Frodo CLI 4.0.0-12 Pre-release
Pre-release

What's Changed

Full Changelog: v4.0.0-11...v4.0.0-12

Frodo CLI 4.0.0-11

24 Feb 16:58

Choose a tag to compare

Frodo CLI 4.0.0-11 Pre-release
Pre-release

What's Changed

Full Changelog: v4.0.0-10...v4.0.0-11

Frodo CLI 4.0.0-9

23 Feb 19:04

Choose a tag to compare

Frodo CLI 4.0.0-9 Pre-release
Pre-release

What's Changed

  • feat: new progress bars that don't overwrite console messaging by @devintrivir in #542

Full Changelog: v4.0.0-8...v4.0.0-9

Frodo CLI 4.0.0-8

23 Feb 04:36

Choose a tag to compare

Frodo CLI 4.0.0-8 Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: v4.0.0-7...v4.0.0-8

Frodo CLI 4.0.0-10

23 Feb 23:14

Choose a tag to compare

Frodo CLI 4.0.0-10 Pre-release
Pre-release

What's Changed

  • Update CLI for apps to allow importing, exporting, and deleting by id in addition to name. by @phalestrivir in #543

Full Changelog: v4.0.0-9...v4.0.0-10

Frodo CLI 4.0.0-7

22 Feb 19:59

Choose a tag to compare

Frodo CLI 4.0.0-7 Pre-release
Pre-release

What's Changed

  • Add IGA flag to connection profile. Add ENV to override it. by @phalestrivir in #541

Full Changelog: v4.0.0-6...v4.0.0-7

Frodo CLI 4.0.0-6

18 Feb 18:45

Choose a tag to compare

Frodo CLI 4.0.0-6 Pre-release
Pre-release

What's Changed

  • New: Added new CLI option to support better control over managed object names by @phalestrivir in #539

Full Changelog: v4.0.0-5...v4.0.0-6

Frodo CLI 4.0.0-5

06 Feb 18:13

Choose a tag to compare

Frodo CLI 4.0.0-5 Pre-release
Pre-release

What's Changed

Full Changelog: v4.0.0-4...v4.0.0-5

Frodo CLI 4.0.0-4

04 Feb 19:01

Choose a tag to compare

Frodo CLI 4.0.0-4 Pre-release
Pre-release

Changed

  • Updated to Frodo Lib 4.0.0
  • Updated binary release to run on Node v24
  • Updated dependencies

Added

  • Added frodo config-manager (fr-config-manager) commands.
  • Added support for Node Designer Nodes through several API and Ops functions to allow for doing exports, imports, deletes, etc. with custom node configurations.
    • Just like with journeys, custom nodes get exported and imported in the same way as they do from AIC/AM, so you can import Frodo exported custom nodes into AIC/AM and vice versa.
    • Additionally, journeys were updated to include custom node dependencies during exports. Even if a journey is exported with Frodo and contains these dependencies in the export JSON, they can still be imported into AIC/AM using the admin UI as it should ignore the custom node dependencies (since AIC/AM doesn't support exporting them yet).
  • Added --retry <strategy> option to all commands.
  • Added the ability to authenticate to an AM classic deployment using Amster credentials (i.e. a public/private key pair). The private key can be in a variety of formats such as PKCS, JWK, and OpenSSH, but is ultimately stored in PKCS#8 format. You can also use encrypted private keys by providing the passphrase when creating the connection profile.

Fixed

  • #XXX:

What's Changed

Full Changelog: v4.0.0-3...v4.0.0-4

Frodo CLI 4.0.0-3

04 Feb 03:00

Choose a tag to compare

Frodo CLI 4.0.0-3 Pre-release
Pre-release

Changed

  • Updated to Frodo Lib 4.0.0

Added

  • Added frodo config-manager (fr-config-manager) commands.
  • Added support for Node Designer Nodes through several API and Ops functions to allow for doing exports, imports, deletes, etc. with custom node configurations.

    Just like with journeys, custom nodes get exported and imported in the same way as they do from AIC/AM, so you can import Frodo exported custom nodes into AIC/AM and vice versa.

    Additionally, journeys were updated to include custom node dependencies during exports. Even if a journey is exported with Frodo and contains these dependencies in the export JSON, they can still be imported into AIC/AM using the admin UI as it should ignore the custom node dependencies (since AIC/AM doesn't support exporting them yet).
  • Added --retry <strategy> option to all commands.
  • Added the ability to authenticate to an AM classic deployment using Amster credentials (i.e. a public/private key pair). The private key can be in a variety of formats such as PKCS, JWK, and OpenSSH, but is ultimately stored in PKCS#8 format. You can also use encrypted private keys by providing the passphrase when creating the connection profile.

Fixed

  • #XXX:

What's Changed

Full Changelog: v4.0.0-2...v4.0.0-3