Buddy is a delivery automation tool that heavily relies on integrations with other services like AWS or Google Cloud.
Until now, the integration was performed at the moment an action has been added for the first time. If you wanted to add more integrations to a service, you had to do it from the Integrations tab in My-ID settings.
However, the solution was not very intuitive, especially for newcomers:
I set up the integration for the first client fine, but for subsequent clients I just see the visible S3 buckets for the first client’s IAM user. It feels like this should possible to make AWS credentials a per project / per pipeline variable, but I can’t see how to do that. Am I missing something or is this a limitation of Buddy’s AWS integration at the moment? Tom Davies, Technical Director at madebykind.com
We’re happy to announce you can now add multiple integrations to your actions without leaving the action details.
Just click the dropdown with the name of your integration and click +Add another:
The change applies to the following actions:
- Deployments: AWS S3, Elastic Beanstalk, CodeDeploy, Lambda, DigitalOcean, Rackspace, Heroku, Shopify, Google Cloud Storage, Google App Engine
- Notifications: Slack
- DevOps: AWS CLI, Heroku CLI, Invoke Lambda function
- Cache invalidation: AWS CloudFront, Google CDN, Cloudflare
Happy delivering with Buddy! 🚚
Buddy is 100% customer driven. If there’s a feature or integration you miss, let us know on the livechat or directly at email@example.com.