Skip to content

Releases: cognitedata/toolkit

v0.2.16

23 Jul 08:15
cc30e42
Compare
Choose a tag to compare

cdf-tk

Changed

  • In the cdf-tk build command, if the Function code cannot be imported, the Toolkit will now give a
    warning instead of an ToolkitValidationError. This is to allow you to deploy code developed in a
    different environment than the environment used to run Toolkit.

Templates

No changes to templates.

Details

Full Changelog: v0.2.15...v0.2.16

v0.2.15

22 Jul 18:23
ae5c7a3
Compare
Choose a tag to compare

cdf-tk

Added

  • [Feature Preview] Support for uploading 3DModel resource to CDF. Note this is the metadata about a 3D model
    Turn on the feature by running cdf-tk features set model-3d --enable.

Fixed

  • Running cdf-tk deploy after a failed build would raise an incorrect ToolkitNotADirectoryError,
    instead of a ToolkitFileNotFoundError for the _build_enviroment.yaml file. This is now fixed.
  • When running cdf-tk deploy with Functions that have not explicitly set cpu, memory, or runtime,
    would always be classified as changed. This is now fixed.
  • [Feature Preview] When dumping assets to csv, headers are no longer repeated for each 1000 asset.
  • [Feature Preview] When dumping assets to parquet, you can now dump more than 1000 assets without
    getting the error TypeError: write() got an unexpected keyword argument 'mode'.
  • [Feature Preview] When dumping assets to parquet/csv, the Toolkit now keeps all asset in memory until it finds
    all unique metadata keys. This is to ensure that header is correct in the resulting parquet/csv file.
  • In the config.[env].yaml, the name parameter in the environment section is no longer required.
    This was supposed to be remove in 0.2.0a4.
  • If you run cdf-tk build --env dev, and then cdf-tk deploy -env prod the Toolkit will
    now raise a ToolkitEnvError.
  • If you run cdf-tk build, the Toolkit will no longer complain about resources that exist in
    CDF but not in the build directory (given that the Toolkit has access to CDF).
  • If you deploy a data model that already exists in CDF, the API will silently fail to update the data model if
    there are any changes to the views in the data model. The Toolkit will now verify that the update of data models
    was successful and raise an error if it was not.

Changed

  • When running cdf-tk deploy for a function the Toolkit checked that it could import the function code
    before deploying the function. This is now removed. The reason is that the toolkit is often run in a
    different Python environment than the function code. This made this check unnecessarily restrictive
    as it would fail even though the function code was correct due to missing dependencies.
  • [Feature Preview] Instead of using functionExternalID+cron expression to identify a function schedule,
    the Toolkit now uses functionExternalID+name. This is to avoid the Toolkit to create multiple schedules
    for the same function if the cron expression is changed and allow to have multiple schedules with the same
    cron expression for the same function. To enable this feature, run cdf-tk features set fun-schedule --enable.

Templates

Added

  • Module cognite_modules/example/cdf_data_pipeline_3d_valhall 3D contextualization
    example pipeline. Reading 3D nodes and matching to asset hierarchy

Details

New Contributors

Full Changelog: v0.2.14...v0.2.15

v0.2.14

15 Jul 12:50
8bd9fdd
Compare
Choose a tag to compare

cdf-tk

Fixed

  • If a container with a direct relation property with a required constraint on another container, the cdf-tk build
    would not give a warning if the required container was missing. This is now fixed.
  • [Feature Preview] In the feature preview, robotics, the properties inputSchema or dataHandlingSchema
    in RobotCapability and DataPostProcessing were not updated correctly. This is now fixed.
  • When running cdf-tk build, with a Node resource. You would get a MissingRequiredIdentifierWarning even though
    the Node had a space/externalId. This is now fixed.
  • In the cdf-tk deploy/clean command, the -i short flag was used for --interactive and --include at the same time.
    This is now fixed, and the -i flag is only used for --interactive.
  • Require cognite-sdk>=7.54.1, this version fixed a bug in the cognite-sdk that caused the cdf-tk to raise
    an CogniteAPIError when deploying or cleaning more than 10 functions.

Templates

No changes to templates.

Details

Full Changelog: v0.2.13...v0.2.14

v0.2.13

10 Jul 13:01
7eb8d80
Compare
Choose a tag to compare

cdf-tk

Fixed

  • [Feature Preview] In the feature preview, cdf-tk import transformation-cli, the Toolkit would fail to convert
    manifest with destination: <string> correctly. This is now fixed.
  • On Windows, when reading files from disk, the Toolkit could raise an UnicodeDecodeError. This is now fixed.
  • [Feature Preview] In the feature preview, robotics, if you tried to update a set of resources in which some
    were existing and others not, the Toolkit would create the new resources. This is now fixed.

Templates

No changes to templates.

Details

Full Changelog: v0.2.12...v0.2.13

v0.2.12

08 Jul 08:55
9d349c3
Compare
Choose a tag to compare

cdf-tk

Added

  • [Feature Preview] Robotic support.

Templates

No changes to templates.

Details

Full Changelog: v0.2.11...v0.2.12

v0.2.11

05 Jul 15:02
47c60e2
Compare
Choose a tag to compare

cdf-tk

Fixed

  • When running cdf-tk build, if you had two files non-YAML files named the same in different modules, or subdirectories
    in the same module, the Toolkit would overwrite the first file with the second file. This is now fixed.

Templates

No changes to templates.

Details

What's Changed

Full Changelog: v0.2.10...v0.2.11

v0.2.10

03 Jul 09:17
234b708
Compare
Choose a tag to compare

cdf-tk

Fixed

  • When running cdf-tk build, if you use subdirectories in a resource directories, and have two resources with the
    same file name, the Toolkit would overwrite the first resource with the second resource. This is now fixed. For
    example, if you have my_module/transformation/subdirectory1/my_transformation.Transformation.yaml and
    my_module/transformation/subdirectory2/my_transformation.Transformation.yaml, the Toolkit would only build the
    second resource.

Templates

No changes to templates.

Details

Full Changelog: v0.2.9...v0.2.10

v0.2.9

02 Jul 13:16
fb1c55a
Compare
Choose a tag to compare

cdf-tk

Changed

  • Tracking usage of Toolkit commands.

Templates

No changes to templates.

Details

Full Changelog: v0.2.8...v0.2.9

v0.2.8

01 Jul 13:50
23706bd
Compare
Choose a tag to compare

cdf-tk

Added

  • [Feature Preview] Option to turn off semantic naming checks for resources. Turn on the feature by running
    cdf-tk features set no-naming --enable.

Fixed

  • When running cdf-tk run function --local, the toolkit would raise an ToolkitValidationError. This is now fixed.
  • When running cdf-tk deploy --dry-run, if any resource was referencing a DataSet, SecurityCategory,
    or ExtractionPipeline, it would incorrectly be classified as changed. This is now fixed. This applied to
    ExtractionPipeline, FileMetadata, Function, Group, Label, TimeSeries, and Transformation resources.

Changed

  • Function configurations for multiple functions can now be in multiple files in the function directory. Before
    all configurations had to be listed in the same YAML file.

Templates

Fixed

  • Added missing dependency to requirements.txt in cognite_modules/examples/cdf_functions_dummy.

Details

What's Changed

Full Changelog: v0.2.7...v0.2.8

v0.2.7

28 Jun 12:42
0d0e05e
Compare
Choose a tag to compare

cdf-tk

Fixed

  • Function schedule for functions with a : in the external id would raise an ValueError.
    This is now fixed.
  • Transformation notifications for transformations with a : in the external id would raise an ValueError.
    This is now fixed.
  • When running cdf-tk deploy, you would get warnings about unrelated resources that were not part of the deployment.
    This is now fixed.
  • The transformations/notifications endpoint was giving 500 errors for requests to non-exising transformations.
    This is now handled by the toolkit and will not raise an error.
  • When doing variable replacement in a sql such as dataset_id('{{dataset_external_id}}'), the toolkit would
    remove the quotes. This is now fixed.