Releases: cognitedata/toolkit
Releases · cognitedata/toolkit
v0.2.16
cdf-tk
Changed
- In the
cdf-tk build
command, if theFunction
code cannot be imported, the Toolkit will now give a
warning instead of anToolkitValidationError
. 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
- [CDF-22141] 🙄Remove function validation on build by @doctrino in #791
- Prepare 0.2.16 by @doctrino in #792
Full Changelog: v0.2.15...v0.2.16
v0.2.15
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 runningcdf-tk features set model-3d --enable
.
Fixed
- Running
cdf-tk deploy
after a failed build would raise an incorrectToolkitNotADirectoryError
,
instead of aToolkitFileNotFoundError
for the_build_enviroment.yaml
file. This is now fixed. - When running
cdf-tk deploy
withFunctions
that have not explicitly setcpu
,memory
, orruntime
,
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 errorTypeError: 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 resultingparquet/csv
file. - In the
config.[env].yaml
, thename
parameter in theenvironment
section is no longer required.
This was supposed to be remove in0.2.0a4
. - If you run
cdf-tk build --env dev
, and thencdf-tk deploy -env prod
the Toolkit will
now raise aToolkitEnvError
. - 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 usesfunctionExternalID
+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, runcdf-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
- fix: catch _build_environment.yaml file missing by @nodegard in #772
- [CDF-22122] 🪓Remove import of function check by @doctrino in #773
- [CDF-22123]💣Feature flag, change how function schedules are identified. by @doctrino in #774
- [CDF-22124] 🏹Avoid redeploying functions by @doctrino in #775
- [CDF-22125] 🤽Support 3D Models by @doctrino in #776
- [CDF-22126] 3D Valhall by @BergsethCognite in #693
- [CDF-22130] 😁 by @doctrino in #781
- [CDF-22128] 🤪 Update 3D model fix by @doctrino in #782
- chore(deps): lock file maintenance by @renovate in #780
- [CDF-22133, CDF-22138] 🏭Asset importer bugs by @doctrino in #783
- [CDF-22136] 🙃fix: not raise if name is not existing by @doctrino in #784
- [CDF-22112] CDF-22112 Verify deploy --env by @doctrino in #785
- [CDF-22127] 👽 Lookup in CDF on build by @doctrino in #786
- [CDF-21893, CDF-22132] Fails to update Data Model by @doctrino in #787
- [CDF-22139] 🤦 Find metadata columns before start writing to disk by @doctrino in #788
- Prep release 0.2.15 by @doctrino in #789
New Contributors
Full Changelog: v0.2.14...v0.2.15
v0.2.14
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 propertiesinputSchema
ordataHandlingSchema
inRobotCapability
andDataPostProcessing
were not updated correctly. This is now fixed. - When running
cdf-tk build
, with aNode
resource. You would get aMissingRequiredIdentifierWarning
even though
theNode
had aspace
/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 thecognite-sdk
that caused thecdf-tk
to raise
anCogniteAPIError
when deploying or cleaning more than 10functions
.
Templates
No changes to templates.
Details
- [CDF-22056] 🦠Required container dependency no warning fix by @doctrino in #754
- [CDF-22057] 🐜Warning on non-existing parent. by @doctrino in #755
- Add limit to asset dump by @doctrino in #756
- [CDF-22072] 👻Splitting resource loaders into multiple files by @doctrino in #758
- [CDF-22064] ⛓️💥Mixpannel connection issues by @doctrino in #761
- [CDF-22062] 🤖😭 by @doctrino in #762
- [CDF-22059] 👺Deploy order views by @doctrino in #763
- [CDF-22074]🫣 by @doctrino in #764
- [CDF-22073]🤡 Complains about node identifier by @doctrino in #765
- [CDF-22058] 🙈Fix used i twice by @doctrino in #768
- [CDF-22071] 👮♂️Fixing up function deployment by @doctrino in #767
- Prepare 0.2.14 by @doctrino in #769
Full Changelog: v0.2.13...v0.2.14
v0.2.13
cdf-tk
Fixed
- [Feature Preview] In the feature preview,
cdf-tk import transformation-cli
, the Toolkit would fail to convert
manifest withdestination: <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
- [CDF-22051]🧑🚒Fix transformation-cli import by @doctrino in #750
- [CDF-22052] 🤖Fix robotics deploy by @doctrino in #751
- Prepare 0.2.13 by @doctrino in #752
Full Changelog: v0.2.12...v0.2.13
v0.2.12
v0.2.11
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
- [CDF-21984] 🧑🚒 Lost SQL files by @doctrino in #737
- Support CDF cmd by @doctrino in #739
- [CDF-22026] 🧑🔧Maintain deploy order in build by @doctrino in #740
- Prepare 0.2.11 by @doctrino in #742
Full Changelog: v0.2.10...v0.2.11
v0.2.10
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 havemy_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
- Docs: update URLs by @doctrino in #733
- [CDF-21976] 🐛Build overwrite bug by @doctrino in #734
- Prepare 0.2.10 by @doctrino in #735
Full Changelog: v0.2.9...v0.2.10
v0.2.9
cdf-tk
Changed
- Tracking usage of Toolkit commands.
Templates
No changes to templates.
Details
- [CDF-21964] 🔻Lower bound for packaging dependency by @doctrino in #728
- [CDF-21967, CDF-21966] 🏴☠️Fast bumping by @doctrino in #729
- [CDF-21971]🛒 Collect message by @doctrino in #730
- Prepare 0.2.9 by @doctrino in #731
Full Changelog: v0.2.8...v0.2.9
v0.2.8
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 anToolkitValidationError
. This is now fixed. - When running
cdf-tk deploy --dry-run
, if any resource was referencing aDataSet
,SecurityCategory
,
orExtractionPipeline
, it would incorrectly be classified as changed. This is now fixed. This applied to
ExtractionPipeline
,FileMetadata
,Function
,Group
,Label
,TimeSeries
, andTransformation
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
incognite_modules/examples/cdf_functions_dummy
.
Details
What's Changed
- [CDF-21947] 🧑🚒Fix run function locally by @doctrino in #716
- [CDF-21949] 🫤Nice indent by @doctrino in #719
- [CDF-21917]🕵️♂️ Fix diffs deploy --dry-run by @doctrino in #720
- [CDF-21945] 😫Less Warnings on Functions by @doctrino in #718
- [CDF-21946] 🤷Turn off naming convention by @doctrino in #717
- [CDF-21895, CDF-21895, CDF-21629] 🛤Feature flag, track commands. by @doctrino in #721
- 😁Prepare 0.2.8 by @doctrino in #726
Full Changelog: v0.2.7...v0.2.8
v0.2.7
cdf-tk
Fixed
- Function schedule for functions with a
:
in the external id would raise anValueError
.
This is now fixed. - Transformation notifications for transformations with a
:
in the external id would raise anValueError
.
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 giving500
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 asdataset_id('{{dataset_external_id}}')
, the toolkit would
remove the quotes. This is now fixed.