Importing existent services
We're building documentation for this section.
Often, cloud resources or other dependencies are already utilized by applications before adopting our structured service framework. nullplatform allows the importation of these pre-existing elements into the service schema, thus building a service catalog based on both existing resources and new ones created under this framework.
Benefits of a Service Catalog
Building a service catalog enables precise knowledge of which applications use which resources. This facilitates traceability and cost management, and also allows control over service parameters in applications.
If the service specification is intended only for importing existing resources, you can set the imported value to true within the selectors field. For more detailed guidance, see the API documentation.
Importing via API
Whenever a service instance is created on nullplatform, a provisioning action is triggered. However, when importing a resource that already exists, this provisioning operation is not necessary. To import a resource, invoke the service creation operation in the following manner:
- The status must be set to
active. - All services schema attributes defined as
requiredmust be provided and conform to their specifications.
Importing via Terraform/OpenTofu Plugin
In scenarios that utilize infrastructure-as-code tools like Terraform/OpenTofu, nullplatform offers compatibility through its dedicated plugin. This integration facilitates the following actions:
- Importing existing services.
- Creating links between services and nullplatform entities.
This compatibility supports the fast adoption of services and enables the rapid generation of a service catalog.