Skip to main content

Cycloid for DevOps teams

Audience​

This section is for DevOps teams who create and maintain Cycloid stacks for end users to use from the service catalog.

Objectives​

At the end of this section, you will master building and managing Cycloid Stacks in the service catalogs available to the end users.

Concepts

A service catalog is a collection of Stacks used by the end users to create new Projects and Environments. For more details on these essential concepts, please go to the reference manual.

A Stack typically contains:

  1. Some automation technologies such as Terraform, Ansible, Helm charts, etc.
  2. A CI/CD pipeline to execute the automation
  3. A StackForms definition file (.forms.yml) to design user-friendly web forms
  4. A Stack metadata file (.cycloid.yml) to describe the Stack

As a DevOps team member, you will create and maintain the Stacks files that will be version-controlled in your Git repository. Your Stacks will typically reside in different folders at the root of your Git repository. Cycloid will crawl your Git repository up to one folder depth maximum to build the service catalogs available to end users via the Cycloid self-service portal.

Prerequisites​

  • A personal Cycloid account with appropriate permissions is required. Typically the user may joined the root organization with at least the Project Manager role.
  • Read access to your Git repositories containing your Cycloid stacks is required.
  • Read and write access to your Git repositories containing your configuration is required.
  • Make sure your Git repository is configured in the Catalog repositories tab from the Stacks page in your Cycloid organization.

Check the config and catalog repository section for more details.

info

If your Git repository is not configured, click the Add catalog repository button in the Catalog repositories tab from the Stacks page in your Cycloid organization.

If you don't have permission to do this action, please contact your Cycloid platform team to configure it.