Default Workflow
When you create a new environment, Atmosly automatically generates a Default Workflow for each application service. This workflow contains the core pipeline stages pre-configured based on your project and environment settings.
Default Stages
| Stage | Description |
|---|---|
| Source | Pre-configured with the repository, branch, and source settings from the environment's service configuration. |
| Build | Pre-configured with the Dockerfile path, build context, and container registry from the service settings. |
| Push | Pushes the built image to the container registry configured for the service. |
| Deploy | Deploys to the environment where the service was created, using automatic deployment by default. |
Workflows operate at the service level. If your application has multiple services (e.g., frontend and backend), each service gets its own distinct default workflow.
Accessing Default Workflows
- Navigate to your Project from the left menu.
- Select the service whose workflow you want to view.
- The default workflow will be listed under the service's workflow section.
Workflow Details View
Clicking on a workflow opens the Workflow Details view — a visual representation of the pipeline stages built with a drag-and-drop canvas.
From this view, you can:
| Action | Description |
|---|---|
| Add Tools | Integrate security scanners (Trivy, detect-secrets, SonarQube) or custom scripts between stages. |
| Modify Stages | Click on any stage node to adjust its configuration — source, build, push, or deploy settings. |
| Execute Workflow | Click Update & Execute Now to save changes and trigger the workflow immediately. |
| View Execution History | Access past execution runs, analytics, and logs. |
| View Reports | Access security and quality scan reports from previous executions. |
| Manage CI Variables | Define build-time variables from the bottom-left panel. |
Deploy-Only Default Workflow
When a service is configured with a Container Registry source (instead of a Git repository), Atmosly generates a deploy-only workflow that skips the Build and Push stages:
| Stage | Description |
|---|---|
| Source | References a pre-built image from the configured container registry and image tag. |
| Deploy | Deploys the referenced image to the target environment. |
Deploy-only workflows are ideal when your images are built externally and you only need Atmosly to handle deployment.