Integrations are used to connect your Shippable CI or CD workflows to third party platforms or services and manage secrets that might be needed by your applications. Examples are tokens, keys, passwords, or even key-value pairs.
The biggest advantages of our design for integrations are:
- Integrations are created in the UI and used with friendly names in your YAML config. This means you do not have to touch your automation scripts when an integration is updated.
- Integrations are securely stored in a Vault store and encrypted at rest and in-flight. Since you do not have to encrypt anything yourself, they are human readable by those who have been granted access.
- Integrations values are not revealed in logs unless you choose to print them out as part of your workflow.
- You can scope each integration to allow or deny access for repositories or roles.
We are big believers in the concept that secrets need to be separated from scripts for better security and privacy.
To learn how to create and manage integrations, read our tutorial on Managing integrations.
Supported integration types
Orchestration Platform Integrations
- Amazon ECS
- Google Container Engine
- Azure DC/OS
- Docker Cloud
- Docker Datacenter
- Joyent Triton
Docker Registry Integrations
- AWS ECR
- Docker Hub
- Docker Trusted Registry
- Docker Private Registry
- Google Container Registry