Configuring a Dedicated Subsystem

To effectively represent a deployment within the Merthin Cloud/Edge Distribution, you begin by configuring a dedicated subsystem. This subsystem is tailored to encapsulate specific aspects of your project, such as a backend API or a web server.

Subsystem Properties and Secrets

Each subsystem is configured with its own set of properties and secrets, which can be crucial for its operation. These configurations are not only vital for the subsystem itself but can also be made accessible to other subsystems within the project. For example, a backend API subsystem may need to utilize credentials stored in a MongoDB subsystem for database access.

Interdependency and Configuration

Moreover, subsystems often depend on each other. For instance, a Heroku-based API subsystem might require properties such as database URLs or user authentication tokens from other subsystems like MongoDB and Auth0. To facilitate this, users must ensure that each subsystem not only exists but is properly configured to share its properties.

Deployment and Version Management

Once configured, the deployment process for the subsystem can be initiated either automatically through a version control system workflow or manually via the CED web interface or the CLI. This deployment process compiles and deploys the subsystem, maintaining a version history that includes details like custom metadata and linked commit hashes. It also supports promotion and rollback capabilities, allowing for robust version control and release management. Important Reminder: Ensure that a connection to the vendor exists and is configured as a subsystem connection prior to the first deployment. This setup is crucial for successful deployment operations.

Programmatic Deployments with Shell-Type Subsystems

Additionally, CED supports a special type of subsystem known as Shell, which allows for programmatic deployments. This functionality provides greater flexibility and control over deployment processes, facilitating complex deployment scenarios that require scripted interactions or automated sequences.

Through these steps, CED users can represent and manage their deployments effectively, ensuring each component integrates seamlessly while maintaining high levels of security and operability.