Description Patterns
Auto-Correlate Pull Requests with Resources in Plural
Plural Supports a number of ways to correlate your Pull Request with resources in Plural, these can 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.
- Deferring merges to off-hours to implement service windows.
- Tie PRs to governance controllers
- Preview Environment Creation
Info:
In all of these cases, it's assumed you have an SCM webhook configured to provide Plural with an event stream for pull request/merge requests from you SCM provider. We support all major SCM providers, and they're easy to set up at Self Service -> SCM Management.
We'll list these all out one-by-one
PR <> Service Correlation
To tie a pull request to a service, simply add a tag like this to the pull requests description body:
Plural Service: {cluster-handle}/{service-name}to your pull request body. Once there, you'll be able to see the pull request in the service's details view in Plural, and once merged, Plural will automatically resync that service with its source of truth in git, allowing for responsive deployment of the new configuration.
If this isn't implemented, the ordinary GitOps sync window is something like ~2m with some jitter