Visit the Composio Enterprise portal to get your Helm chart:
Enterprise Installation Replicated migration guide
-
OpenTelemetry (OTEL) Configuration - Configure OpenTelemetry for observability and monitoring. View Guide
-
Datadog Alerts Setup - Set up alerts and monitoring using Datadog. View Guide
-
Object Store Configuration
- Azure Blob Storage - Configure Azure Blob Storage for Apollo. View Guide
- S3 Storage - Configure S3-compatible storage (AWS S3, GCP GCS) for Apollo. View Guide
-
Frontend Configuration
- Composio Frontend - Configure the Composio frontend. View Guide
- SMTP Setup - Configure SMTP for email functionality. View Guide
composio/values-managed-vpc.yaml configures external dependencies, workload IAM,
prepared secrets/service accounts, database TLS and Fargate-compatible resources.
Merge public customer settings and immutable application image references over it.
The deployment runner supplies actual resource references and secret values.
Package a single release with its already tested runner image:
node scripts/package-replicated-release.mjs \
--version 0.2.14-managed-vpc-test.2 \
--runner-publication /path/to/publication.json \
--chart-reference oci://registry.replicated.com/composio-rodent/managed-vpc-test/composio \
--values /path/to/public-managed-vpc-values.yaml \
--qualification /path/to/qualification.json \
--output /path/to/new-release-directoryThe publication record must declare runner contract version 2 and the embedded infrastructure hash. The generated chart and release lock bind the runner image, source revision, infrastructure, chart content and application image digests. There is no separate infrastructure chart or archive download. The bootstrap package is included as a local companion. Packaging never pushes or deploys. Without explicit qualification, output is a candidate rather than a deployment lock. Qualification must describe the integrations and features actually tested. Keep customer licenses, personalized chart archives and credential values outside Git. The customer initializes its S3/KMS Pulumi stack once, reviews a real preview, and approves the same pinned release before infrastructure and Helm deployment.