Setting up Azure DevOps Pipelines with the Cognite Toolkit

​@Khilesh Sahu It looks like the documnetation needs to be updated. The ado-pipeline feature is no longer an alpha feature from version 0.4.0 onwards. 

Thank you for reporting this. I’ll inform the documentation team regarding this.

FYI ​@Anders Albert 

​@Mithila Jayalath ​@Anders Albert 

Thanks Mithila for clarifying it.

Do we still have to add the feature flag in cdf.toml?

Also, I see that .devops folder get created as per docs but where my views, containers, space and data models yaml files should be located. Documentation mostly mentioned about .devops and deployment but not clarify where all resources yaml files should be located.

Additionally, lets say we want to maintain different versions of views and model. Later, deploy specific versions using toolkit so how should be the folder structure and what would be recommended steps to approach it?

Do we still have to add the feature flag in cdf.toml?

​@Khilesh Sahu No need to have the feature flag in the `cdf.toml`. Will update the docs.

Also, I see that .devops folder get created as per docs but where my views, containers, space and data models yaml files should be located. Documentation mostly mentioned about .devops and deployment but not clarify where all resources yaml files should be located.

The resource YAML should be located in the modules folder, as described in the setup guide. https://docs.cognite.com/cdf/deploy/cdf_toolkit/guides/setup#step-3-initialize-the-configuration-files-and-modules

Additionally, lets say we want to maintain different versions of views and model. Later, deploy specific versions using toolkit so how should be the folder structure and what would be recommended steps to approach it?

Currently we do not have a general recommendation for how to maintain multiple versions of the same views. You have typically two ways, either you maintain one YAML file for each version or you only have the latest. I would maintain two versions if both are in use, thus needs to be governed. If the previous version is no longer in use, I think it sufficient to have the older one in your version control history, and only actively govern the latest.

​@Anders Albert  thank you for prompt reply.

I tried to have folder structure like /modules/data_models, however I am getting following error:

ERROR (ToolkitMissingModuleError): The following selected modules are missing,

please check path: {PosixPath('modules')}.

HINT A module is a directory with one or more resource directories in it.

Available resource directories are ['3dmodels', 'auth', 'classic',

'data_models', 'data_sets', 'extraction_pipelines', 'files', 'functions',

'hosted_extractors', 'locations', 'raw', 'robotics', 'streamlit', 'timeseries',

'transformations', 'workflows']

So when I tried again with structure like /modules/custom/my_module/data_models. Then it works fine.

I tried this because when I ran toolkit from my local machine and selected following option during cdf modules init then it created similar folder structure. Other option did not work for me that time:
 

But this too much folder levels for me I would like to have only /modules/data_models.

Here is my config.dev.yaml selected module part
environment:
  name: dev
  project: <my-project>
  type: dev
  selected:
  - modules/

So if I can give very specific folder path for “modules” in config.dev.yaml then I would be able to manage different versions of data models using different folders.

​@Anders Albert / ​@Mithila Jayalath  - awaiting response

​@Anders Albert / ​@Mithila Jayalath  - any update on this?

Yes ​@Anders Albert, thank you 😊