Skip to content

Commit 2e2b5b8

Browse files
feat: adjusted placement of CLI command
Adjusted placement of CLI command and added codetabs
1 parent 43a3186 commit 2e2b5b8

File tree

2 files changed

+77
-48
lines changed

2 files changed

+77
-48
lines changed

sites/platform/src/learn/overview/build-deploy.md

Lines changed: 39 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -118,13 +118,40 @@ Note that development environments **always** use automatic deployment, while ma
118118

119119
### Change deployment type
120120

121-
You can adjust deployment behavior in your environment (staging or production only). To switch to manual, navigate to the environment settings in the Console and select the manual deployments option.
121+
You can adjust deployment behavior in your environment (staging or production only).
122122

123-
{{< note theme="tip" >}}
123+
{{< codetabs >}}
124124

125-
As soon as your deployment type is switched from automatic to manual, all currently staged changes are deployed immediately and the environment resumes its default automatic deployment behavior.
125+
+++
126+
title=Using the CLI
127+
+++
126128

127-
{{< /note >}}
129+
Use the following command in the CLI to view or change the deployment type:
130+
131+
```bash
132+
platform environment:deploy:type
133+
```
134+
The output should look similar to the example below:
135+
136+
```bash
137+
Selected project: [my-project (ID)]
138+
Selected environment: main (type: production)
139+
Deployment type: manual
140+
```
141+
142+
For more information about how this command works, use:
143+
144+
```bash
145+
platform environment:deploy:type --help
146+
```
147+
<--->
148+
+++
149+
title=Using the Console
150+
+++
151+
152+
To switch to manual, navigate to the environment settings in the Console and select the manual deployments option.
153+
154+
{{< /codetabs >}}
128155

129156
### Trigger deployment manually
130157

@@ -136,7 +163,7 @@ Once manual deployment is enabled, eligible changes are staged. You can deploy t
136163
title=Using the CLI
137164
+++
138165

139-
Deploy staged changes to your chosen environment:
166+
Deploy staged changes to your chosen environment using the following command:
140167

141168
```bash
142169
platform environment:deploy
@@ -155,24 +182,6 @@ Deploying staged changes:
155182
| fq73u53ruwloq | 2024-11-22T12:06:17+00:00 | Pilar pushed to main | success |
156183
+---------------+---------------------------+-----------------------------------------------------------+---------+
157184
```
158-
You can also use the following command to view or change the deployment type:
159-
160-
```bash
161-
platform environment:deploy:type
162-
```
163-
The output should look similar to the example below:
164-
165-
```bash
166-
Selected project: [my-project (ID)]
167-
Selected environment: main (type: production)
168-
Deployment type: manual
169-
```
170-
171-
For more information about how this command works, use:
172-
173-
```bash
174-
platform environment:deploy:type --help
175-
```
176185
<--->
177186
+++
178187
title=Using the Console
@@ -193,6 +202,13 @@ POST /projects/{projectId}/environments/{environmentId}/deploy
193202

194203
{{< /codetabs >}}
195204

205+
{{< note theme="tip" >}}
206+
207+
As soon as your deployment type is switched from automatic to manual, all currently staged changes are deployed immediately and the environment resumes its default automatic deployment behavior.
208+
209+
{{< /note >}}
210+
211+
196212
## Deployment philosophy
197213

198214
{{% vendor/name %}} values consistency over availability, acknowledging that it's nearly impossible to have both.

sites/upsun/src/learn/overview/build-deploy.md

Lines changed: 38 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -118,13 +118,40 @@ Note that development environments **always** use automatic deployment, while ma
118118

119119
### Change deployment type
120120

121-
You can adjust deployment behavior in your environment (staging or production only). To switch to manual, navigate to the environment settings in the Console and select the manual deployments option.
121+
You can adjust deployment behavior in your environment (staging or production only).
122122

123-
{{< note theme="tip" >}}
123+
{{< codetabs >}}
124124

125-
As soon as your deployment type is switched from automatic to manual, all currently staged changes are deployed immediately and the environment resumes its default automatic deployment behavior.
125+
+++
126+
title=Using the CLI
127+
+++
126128

127-
{{< /note >}}
129+
Use the following command in the CLI to view or change the deployment type:
130+
131+
```bash
132+
upsun environment:deploy:type
133+
```
134+
The output should look similar to the example below:
135+
136+
```bash
137+
Selected project: [my-project (ID)]
138+
Selected environment: main (type: production)
139+
Deployment type: manual
140+
```
141+
142+
For more information about how this command works, use:
143+
144+
```bash
145+
upsun environment:deploy:type --help
146+
```
147+
<--->
148+
+++
149+
title=Using the Console
150+
+++
151+
152+
To switch to manual, navigate to the environment settings in the Console and select the manual deployments option.
153+
154+
{{< /codetabs >}}
128155

129156
### Trigger deployment manually
130157

@@ -136,7 +163,7 @@ Once manual deployment is enabled, eligible changes are staged. You can deploy t
136163
title=Using the CLI
137164
+++
138165

139-
Deploy staged changes to your chosen environment:
166+
Deploy staged changes to your chosen environment using the following command:
140167

141168
```bash
142169
upsun environment:deploy
@@ -155,26 +182,6 @@ Deploying staged changes:
155182
| fq73u53ruwloq | 2024-11-22T12:06:17+00:00 | Pilar pushed to main | success |
156183
+---------------+---------------------------+-----------------------------------------------------------+---------+
157184
```
158-
159-
You can also use the following command to view or change the deployment type:
160-
161-
```bash
162-
upsun environment:deploy:type
163-
```
164-
The output should look similar to the example below:
165-
166-
```bash
167-
Selected project: [my-project (ID)]
168-
Selected environment: main (type: production)
169-
Deployment type: manual
170-
```
171-
172-
For more information about how this command works, use:
173-
174-
```bash
175-
upsun environment:deploy:type --help
176-
```
177-
178185
<--->
179186
+++
180187
title=Using the Console
@@ -195,6 +202,12 @@ POST /projects/{projectId}/environments/{environmentId}/deploy
195202

196203
{{< /codetabs >}}
197204

205+
{{< note theme="tip" >}}
206+
207+
As soon as your deployment type is switched from automatic to manual, all currently staged changes are deployed immediately and the environment resumes its default automatic deployment behavior.
208+
209+
{{< /note >}}
210+
198211
## Deployment philosophy
199212

200213
{{% vendor/name %}} values consistency over availability, acknowledging that it's nearly impossible to have both.

0 commit comments

Comments
 (0)