You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ce/features/plan-persistence.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,4 +2,4 @@
2
2
title: "Plan Persistence"
3
3
---
4
4
5
-
By default digger will run an apply based on the branch pullrequest files (no artefacts stored). In order to configure plan artefacts you can configure the inputs for storing as github artefacts or aws buckets or gcp buckets. The corresponding artefacts to be configured can be found in [storing plans in a bucket](/ce/howto/store-plans-in-a-bucket)
5
+
By default, Digger runs the apply step on the pull-request branch files (no artifacts are stored). To enable plan artifact persistence, configure the inputs to store them as GitHub artifacts, AWS buckets, or GCP buckets. The corresponding artifacts are documented in [storing plans in a bucket](/ce/howto/store-plans-in-a-bucket).
0 commit comments