What makes up your service?

Each service built with Omnistrate platform is a collection of service components, parameters, features, and infrastructure configurations. Omnistrate will use all those to determine which parameters it needs to request from your customers, which resources need to be deployed, and how they need to be deployed each time a new deployment is created.

Defining your service

There are multiple ways to define a service. In addition to using UI where you are guided throughout the process, there are various ways to define a service in declarative way:

• Compose spec - Format that extends the Docker compose specification with additional Omnistrate specific elements. You can learn more about these extensions here.
• Service plan spec - The Service plan spec is a format used to define your service structure when onboarding your Helm charts, Kubernetes operators, Terraform scripts, or Kustomize scripts. For more details, see helm-charts documentation.

Having the service defined in one of the above formats, allows you to store the service definition in a code repository of your choice and automate service updates. If you need even more control over the process, you can use the Omnistrate API to define service programmatically. For API reference, see here.