Introducing Secure Webhook Deployment Triggers

In our ongoing efforts to add more flexibility and efficiency to your development workflows, we're excited to announce a new feature of Ampt's built in CI/CD service: Secure Webhook Deployment Triggers. This new feature is designed to provide teams with a more dynamic and versatile approach to automating deployments, adding capabilities to your deployment pipelines beyond traditional git-based triggers.

What Are Secure Webhook Deployment Triggers?

Secure Webhook Deployments Triggers allow you to trigger app rebuilds and deployments through a secure, URL-based webhook. This means you can now initiate deployments directly from events outside of your source code repository, such as content updates in a headless Content Management System (CMS) or from scheduled tasks, without the need for a git commit.

Key Benefits

Flexibility in Triggering Deployments: You can trigger a deployment from virtually anywhere that can send an HTTP POST request. This is particularly useful for projects utilizing a headless CMS. When content changes, you can now trigger a redeployment, keeping your site or app up-to-date without manual intervention or a git commit.

Simplified Workflows for Scheduled Tasks: Scheduled tasks, such as nightly builds or content synchronization, can now trigger deployments, streamlining operations and ensuring that your application is always running the latest version of its content or dependencies.

Deployment Without Direct GitHub Integration: For projects not connected to GitHub, this feature offers a way to deploy applications using the most recent deployment archive of the app. This ensures that you can still maintain a robust deployment pipeline, even for projects that don't use traditional VCS platforms.

How It Works

Secure Webhook Deployment Triggers leverage a unique, secure URL generated using the Ampt Dashboard. You can call this URL with an HTTP POST request, triggering a new build and deployment process. If connected to a GitHub repository, the service can use the latest commit in the selected branch. If not connected to a GitHub repository (or if preferred), the service will use the latest successful archive of your application for this process, ensuring that deployments are always based on the most stable version available.

Note that only one webhook request per environment can be processed at a time. While a deployment is running, the system will queue any additional webhook requests. Also, there is a limit of one trigger call per minute, per webhook. If you repeatedly call one of the endpoints, accidentally or intentionally, it will block those attempts for up to a minute.

Getting Started

To begin using Secure Webhook Deployment Triggers, open the Ampt Dashboard and navigate to your app's settings page. Click on the "Webhooks" option. Click the "+" option to configure a new secure webhook URL.

Once created, this URL can be integrated into your headless CMS, scheduled tasks, or any other system capable of making HTTP requests, to trigger deployments as needed.

For detailed instructions on setting up CI/CD pipelines with Ampt, please refer to our documentation.

Start Revolutionizing Your Workflows

We think Secure Webhook Deployments will add lots of flexibility to your automated CI/CD pipelines, offering a more dynamic deployment process and opening up new integration possibilities. As always, we'd love to hear your feedback and experiences as you incorporate this new feature into your development workflows. Please be sure to join our community on Discord to share your thoughts. And get ready for plenty more updates and enhancements to come. 😉

Happy deploying!