Port's self-service actions support a variety of backends that can be triggered when a user invokes an action.
Here is the basic backend model:
The Port-backend integration includes the following steps:
- The action is triggered in Port - the trigger can be either a user interacting with the self-service actions UI, or an automation triggering an action via the API;
- Port generates the event payload - the payload includes metadata about the invoked action and the user inputs;
- The payload is sent to your backend - the backend can be a URL, a dedicated Kafka topic or one of your CI/CD workflows and pipelines;
- Your backend receives the payload and handles the request - depending on the action, the backend might open a PR, create a new cloud resource, provision a new environment etc.;
- Your backend updates Port on the status of the execution - You can enrich the action run object in Port by adding logs, attaching links to other workflows or pipelines that help fullfil the request and add a final success/fail status once the action is complete.
🗃️ Port Execution Agent
🗃️ Webhook Actions
🗃️ GitHub Workflow Actions
🗃️ GitLab Pipelines Actions
🗃️ Jenkins Pipeline Actions
🗃️ Azure Pipeline Actions
📄️ Cloud Build Pipeline Trigger
In this guide, you will learn how to trigger your Cloud Build Pipelines from Port, using Webhook Actions.
🗃️ Kafka Actions
📄️ Terraform Cloud Actions
Port's Terraform Cloud Action can trigger
📄️ Circle CI Actions
Port's Circle CI Action can trigger