Release v2.2.3

no functional changes compared to v2.2.2

• this release fixed a poetry/docker build issue
• the v2.2.2 branch was not a proper release, but a branch with this name, explaining why it doesn't appear in "/releases"
• as the v2 branch is still providing the :latest release but is in main branch overtaken by v3-beta. This release is tagging the branch fix/v2-release-fix w/o a PR required

Full Changelog: v2.2.1...v2.2.3

Pre-Release v3.0.0-beta3 (security release only)

Pre-Release v3.0.0-beta3 (security release only)

This is a PRE-RELEASE tagged as v3.0.0-beta3 and it is still under internal testing and review.

• you can use it as gh-action like this

- uses: cognitedata/inso-extpipes-cli@v3.0.0-beta3

changes

1. Dependencies were updated (running poetry update) to mitigate security warnings
2. gh-action updated to be aligned with bootstrap-cli, and fix a DOCKERHUB secret access issue (using wrong environment)

Full Changelog: v3.0.0-beta2...v3.0.0-beta3

Pre-Release v3.0.0-beta2

This is a PRE-RELEASE tagged as v3.0.0-beta2 and it is still under internal testing and review.

• you can use it as gh-action like this

- uses: cognitedata/inso-extpipes-cli@v3.0.0-beta2

What's Changed

• Update base.py by @janne123456789 in #30

New Contributors

• @janne123456789 made their first contribution in #30

Full Changelog: v3.0.0-beta1...v3.0.0-beta2

Pre-Release v3.0.0-beta1

This is a PRE-RELEASE tagged as v3.0.0-beta.1 and it is still under internal testing and review.

• you can use it as gh-action like this

- uses: cognitedata/inso-extpipes-cli@v3.0.0-beta1

It is a BREAKING-CHANGE because

• the configuration structure changed
  • before being rawdb centric, it is now a list of pipelines
• a complete code-refactoring happened
• speedup in usage as we switched to publish an image to dockerhub, instead of building the image every time in a gh-action
• support for Azure DevOps is under testing

Release v2.2.1

no functional changes compared to v2.2.0

• this release was an internal housekeeping, fixing a code-quality gh-action issue
• pls refer to release-notes v2.2.0 for latest changes

Fix

• pre-commit: Fix for failing gh-action pre-commit job (#23) (b3340c1)

Release v2.2.0

New configuration feature

• added pipeline level boolean parameter skip-rawtable to allow control over creation of raw-table
  • feature request, based on discussion and feedback from Cognite Bootcamp training
  • README and example configuration file are updated with details
• if you want to use the new feature:
  • update your config-file
  • and update your GitHub Action tag to uses: cognitedata/inso-expipes-cli@v2.2.0

Background

• the actual v2 configuration syntax is RAWDB centered, which is not reflecting reality anymore
  • raw-tables are an optional element creating an extpipe (this was not the assumption, when this tool was created)
  • next release and switch to a new (breaking) v3 configuration-syntax will express this change and move the rawdb element from top to a configuration leaf

PR and issue

• skip-rawtable: Adding feature skip-rawtable (#22) (f73e345)

Release v2.1.0

New configuration feature added

• based on user feedback after our Cognite Bootcamp training, this feature was added
• You can now take control over the automatic-delete
  • which by default deletes extpipes, which are not covered by the given configuration file.
  • In other words the default behavior helps you too keep your CDF deployment in sync with your configuration

The feature to override this default behavior is available:

1. Through the configuration file, which is the only option when used from GitHub Action:

# new since v2.1.0
# The default and recommended value is: true
# to keep the deployment in sync with configuration
# which means non configured extpipes get automatically deleted
automatic-delete: true

2. As a command-line parameter

➟  extpipes-cli deploy --help
Usage: extpipes-cli deploy [OPTIONS] [CONFIG_FILE]

  Deploy a set of extpipes from a config-file

Options:
  --debug                      Print debug information
  --automatic-delete [yes|no]  Purge extpipes which are not specified in
                               config-file automatically (this is the default
                               behavior, to keep deployment in sync with
                               configuration)
  -h, --help                   Show this message and exit.

(see PR #21) (db295cd) for details)

Release v2.0.2

Fix

• create: Switch to one by one create (#14) (d58e62d)

Release v2.0.1

Fix

• Fixing the main branch name from workflow (6ebda8c)

v0.9 pre-release

Releasing the v0.9 CLI (with gh-action support) to deploy and maintain CDF Extraction Pipelines.

The main feature is a simple-structured YAML configuration file, which will create (or update / delete) CDF Extraction Pipelines.
The design is tightly coupled with latest https://github.com/cognitedata/inso-bootstrap-cli realease.

More to come (documentation, examples, test-case coverage, ...).
This is a pre-release and can be implemented with Cognite SCS teams (ex InSo -> Industry Solution).