Skip to content

v0.3.0

Choose a tag to compare

View all tags
@doctrino doctrino released this 08 Oct 10:14
v0.3.0
4c108bd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

cdf

Added

  • Added support for device code login flow.
  • Support for CogniteFiles.
  • Docker release of the Toolkit.
  • Support for Hosted Extractors.
  • If there are multiple cognite_toolkit_service_principals, the cdf auth verify will offer to delete duplicates.
  • Dump for Assets and TimeSeries with cdf dump asset and cdf dump timeseries commands.
  • The new cdf modules add subcommand lets users add modules to an existing modules directory.
  • Added support for resource type Sequence in the classic folder.
  • Made the config.[env].yaml optional when running the `cdf build command.
  • Loaders for resource types Assets, 3DModel, and Robotic (Map, DataPostProcessing, RobotCapability,
    Frame, and Location). These loaders were earlier available as feature preview.
  • Support for LocationFilter in the locations folder.
  • Command cdf repo init to initialize the repository with .gitignore, .env, and if the user is on GitHub, creates default workflows for running Toolkit in CI/CD.
  • Command cdf modules list to list all modules.
  • Command cdf modules init to setup modules. This is interactive and will guide you through selecting the
    modules you want to use. You can bypass the interactive mode by using the --all flag. which
    will select all modules, similar to the previous cdf-tk init command.
  • Command cdf modules upgrade to upgrade all modules automatically.

Changed

  • Running cdf dump datamodels now dumps containers and views into separate folders.
  • When running deploy --dry-run, the Toolkit will not require write access to the CDF project.
  • The Toolkit no longer gives a warning if it cannot import Cognite Function code when executing the cdf build
    command. This is to separate the build and deploying of artifacts from validating/debugging the function code.
    Validation of the function code is expected to be handled by cdf run function local.
  • [BREAKING] The resource folder timeseries_datapoints is removed and csv and parquet files with
    datapoints are now expected to be in the timeseries folder.
  • The dump of data models has changed interface, now the data model id is optionally given as positional instead
    of flags. If now data model is given, the user will be prompted to select one.
  • Added flag --modules/-m to select which modules to build in the cdf build command.
  • The cdf build command no longer requires config.[env].yaml to be present. If it is not present, the Toolkit
    will use the default values for the environment.
  • [BREAKING] The command cdf auth verify has been split into cdf auth init and cdf auth verify. The init command
    is used to initialize the auth parameters, and the verify command is used to verify that required privileges are
    set. The init command will by default run the verify command after the initialization unless a --no-verify
    flag is set. In addition, the two commands have been reworked to be more user-friendly. They are now interactive
    (no longer requires a --interactive flag) and have no longer supports passing in a custom Group file. Instead,
    they are intended to only set up and verify a service principal for the Toolkit.
  • The WorkflowTrigger config files now supports object (dict) as a valid type for the
    data field. This will automatically be converted to a json string when deploying the trigger.
  • In the commands build and pull, modules upgrade and modules list, organization-dir is now an
    optional argument --organization-dir and -o instead of positional argument. This is to have consistent
    behavior with other commands.
  • The resource FunctionSchedule is not uniquely identified by name instead of cronExpression by the Toolkit.
    This enables multiple schedules with the same cron expression for the same function.
  • The Toolkit no longer gives warnings for naming conventions that are not followed.
  • [BREAKING] The resource Label is now in the resource folder classic and not in the labels folder.

Fixed

  • Uploading a file will no longer overwrite the FileMetadata.
  • Running cdf auth verify now prompts the user to create the cognite_toolkit_service_principal group if it does not exist.
  • In the cdf build command, version variables (DataModel, View, Transformations) are now always read as
    string and not integer. This ensures no false positive warnings for missing dependencies.
  • In the cdf deploy/clean command, if a transformation is writing to a DataModel or a View the version is
    now always read as a string. Before if it was for example, 3_0_0 it would be read as 300 and cause
    the deployment of the transformation to fail.
  • If you removed metadata in any resource file, the Toolkit would not update this change in CDF. This is now fixed.
  • The config value of a ExtractionPipelineConfig is now correctly parsed as a string. Before it was parsed as YAML,
    typically an object/dict, which caused loss of information. This is because
    yaml.safe_dump(yaml.safe_load(config)) != config as, for example, special YAML tags are lost.
  • The field default_organization_dir was not read in the cdf.toml file. This is now fixed.
  • If the version of a DataModel or View was set to 1_0_0 in the resource file, Toolkit would send
    it as 100 to the API. This is now fixed.
  • Groups without metadata no longer triggers redeploy when running cdf deploy
  • When running any command, the terminal would print warnings from the cognite-sdk. This is now fixed.

Removed

  • CSV files in the timeseries_datapoins folder with the string timeshift_ in the index will no longer
    be timeshifted to today when running cdf build
  • FileMetadata pattern $FILENAME is no longer supports prefix and suffix in the name parameter. This is to
    simplify the pattern.
  • [BREAKING] The command cdf describe is removed. This functionality was not used and thus removing it to simplify
    the Toolkit and to focus on the core functionality.
  • [BREAKING] Support for api parameters in Node resource is removed.
  • Toolkit no longer support Python 3.9.
  • The --interactive flag from the cdf deploy and cdf clean commands.
  • The shared flags --verbose. This has been deprecated and has been replaced by --verbose on each individual
    command. For example, before you could write cdf --verbose build --env dev, now you should write
    cdf build --env dev --verbose.
  • [BREAKING] The command cdf-tk init it now replaced by cdf repo init and cdf modules init.

Templates

Added

  • CogniteCore full and minimum extension templates in quickstart and example packages.
  • Added bootcamp modules ice_cream_api and oee.
  • New modules cognite_modules/inrobot.

Details

What's Changed

New Contributors

Full Changelog: v0.2.20...v0.3.0

Contributors

spex66, ronpal, and 6 other contributors
Assets 2
Loading