DevOps

Snoweaver offers comprehensive functionalities to support the DevOps lifecycle, including:

Import and Export

Project resources can be imported and exported as YAML documents through the project console or via API procedures. You can choose to retrieve or update records directly or as files through the CODE stage.

When importing or exporting resources as files, the following options are available:

  • Specify whether to perform the operation on a resource type, a specific resource, or all resources.

  • Option to purge all resources within the project before importing.

  • Option to purge the CODE stage before exporting.

Resource files are named following the convention: <resource_type>_<resource_name>.yaml. When a file is imported, Snoweaver will either create or update the specific resource based on the file name.

Using the project console

On the home page of each project, you’ll find import/export functionalities. You can choose to import or export resources as files, or simply print the record on the screen.

../_images/112.png

Calling API procedures

Snoweaver offers a range of API Procedures for managing both global and project-specific resources. Additionally, we provide a shell command-line tool, Snoweaver CLI, which simplifies the usage of these API procedures.

Integrating with a Version Control System

Snoweaver seamlessly integrates with version control systems through API procedures for importing and exporting resources.

By leveraging the API Procedures and Snoweaver CLI, developers can efficiently use their preferred IDEs for job development and configuration.

Tutorial: Integrate a project with Github

Tutorial: Job development using a client machine

CI / CD

Snoweaver seamlessly integrates with any DevOps pipeline using the API Procedures and Snoweaver CLI.

For more information, refer to:

Tutorial: Build a CI/CD pipeline with Github actions