Description Patterns
Auto-Correlate Pull Requests with Resources in Plural
Plural supports several ways to correlate your pull requests with resources in Plural. These serve a variety of purposes:
- Kick a Plural Service to minimize GitOps lag on merge.
- Auto-generate Plural Stack plans for Terraform changes, improving the pull request review process.
- Defer merges to off-hours to implement service windows.
- Tie PRs to governance controllers.
- Create preview environments.
Info:
In all of these cases, it's assumed you have an SCM webhook configured to provide Plural with an event stream for pull requests/merge requests from your SCM provider. We support all major SCM providers, and webhooks are easy to set up at Self Service -> SCM Management.
We'll cover each of these one by one.
PR <> Service Correlation
To tie a pull request to a service, add a tag like this to the pull request's description body:
Plural Service: {cluster-handle}/{service-name}Once it's there, you'll be able to see the pull request in the service's details view in Plural, and once it's merged, Plural will automatically resync that service with its source of truth in Git, allowing for responsive deployment of the new configuration.
Without this tag, the ordinary GitOps sync window is roughly 2m with some jitter.