Create an isolated application environment for a pull request. A preview blueprint defines the resources and triggers for that environment.
You will need the following to get started:
- A connected Git source and an application that builds successfully
- A list of the services, jobs, databases, and secrets required by the application
- A decision about the data and external resources that each preview can access
1. Define the preview boundary
List the resources that each preview needs. Decide which resources the preview creates and which resources it shares. Keep production credentials and data out of previews unless your access policy permits that use.
Use environments to organize the application resources. Review secret groups for the variables that those resources need.
2. Create a preview blueprint
Create and configure a preview blueprint. Configure its repository triggers and resource definitions for the application.
For a guided example that includes a build service and workflows, use the environment tutorial. Use the same resource names and connection values throughout that setup.
3. Create a preview from a pull request
Use a pull request that matches the configured trigger. Inspect the preview and its resource states.
Make sure that the preview uses the intended revision. Open the application and exercise a request that uses its dependencies. If a resource fails, examine its logs before changing the blueprint.
4. Define cleanup
Review preview teardown in Manage preview blueprints. Make sure that the cleanup behavior matches your data-retention requirements.
If templates manage other resources, review their teardown workflows. Identify shared resources before adding deletion steps.
The setup is complete when a matching pull request creates a working preview and the preview lifecycle handles its resources as intended.