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
# Specific environment variables that fit your context (e.g. offline)
51
+
env:
52
+
MY_VAR1: 'my_value'
53
+
MY_VAR2: ${{ secrets.MY_VAR2 }}
54
+
```
55
+
56
+
Alternatively, you can use it in a Drone pipeline (`type: docker`).
19
57
20
58
```yaml
21
59
steps:
@@ -52,11 +90,11 @@ steps:
52
90
The following resumes what Victor does for you.
53
91
54
92
<div align="center">
55
-
<img src="res/how-it-works.png" alt="How it works in a Drone pipeline">
93
+
<img src="res/how-it-works.excalidraw.png" alt="How it works in a Drone pipeline">
56
94
</div>
57
95
58
96
Here are more explanation:
59
-
1. **Get stack if exist**: Victor create a new Pulumi workspace in your Drone pipeline, then create a stack, and if the webserver contains a state file, loads it. This enable the following to work properly.
97
+
1. **Get stack if exist**: Victor create a new Pulumi workspace in your GitHub Action workflow or Drone pipeline, then create a stack, and if the webserver contains a state file, loads it. This enable the following to work properly.
60
98
2. **Update**: by comparing the existing and actualised resources (does a refresh first) to the target, Victor enable fine-grained continuous deployment of your resources.
61
99
3. **Push updated stack**: finally, Victor exports the stack state file and uploads it in the webserver such that future iterations will be able to load it, to really do **continuous** deployment.
0 commit comments