@proggarapsody/bitbottle 1.28.0 → 1.29.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +36 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -82,6 +82,8 @@ Credentials are stored in `~/.config/bitbottle/hosts.yml`. Inside a git repo wit
|
|
|
82
82
|
| `webhook` | `list` `view` `create` `delete` |
|
|
83
83
|
| `commit` | `log` `view` `status` `comment {list\|add\|edit\|delete}` |
|
|
84
84
|
| `pipeline` | `list` `view` `run` _(Cloud only)_ |
|
|
85
|
+
| `deployment` | `list` `view` _(Cloud only)_ |
|
|
86
|
+
| `environment` | `list` `create` `delete` `variable {list\|set\|delete}` _(Cloud only)_ |
|
|
85
87
|
| `workspace` | `list` _(Cloud only)_ |
|
|
86
88
|
| `project` | `list WORKSPACE` _(Cloud only)_ |
|
|
87
89
|
| `issue` | `list` `view` `create` `close` `edit` `reopen` `assign` `comment {list\|add\|edit\|delete}` _(Cloud only)_ |
|
|
@@ -205,6 +207,40 @@ Secured variables redact their value on read (TTY column shows
|
|
|
205
207
|
`<secured>`, JSON `value` shows `"<secured>"`). Use `--body=-` to read
|
|
206
208
|
the value from stdin so the secret never touches shell history.
|
|
207
209
|
|
|
210
|
+
### Deployments & Environments _(Cloud only)_
|
|
211
|
+
|
|
212
|
+
```bash
|
|
213
|
+
# List recent deployments
|
|
214
|
+
bitbottle deployment list MYWORKSPACE/my-service
|
|
215
|
+
bitbottle deployment list MYWORKSPACE/my-service --limit 25
|
|
216
|
+
|
|
217
|
+
# View a single deployment
|
|
218
|
+
bitbottle deployment view MYWORKSPACE/my-service {deployment-uuid}
|
|
219
|
+
|
|
220
|
+
# List environments
|
|
221
|
+
bitbottle environment list MYWORKSPACE/my-service
|
|
222
|
+
|
|
223
|
+
# Create an environment (type must be Test, Staging, or Production)
|
|
224
|
+
bitbottle environment create MYWORKSPACE/my-service --name "QA" --type Test
|
|
225
|
+
bitbottle environment create MYWORKSPACE/my-service --name "Prod" --type Production --rank 10
|
|
226
|
+
|
|
227
|
+
# Delete an environment (destructive — --confirm required on non-TTY)
|
|
228
|
+
bitbottle environment delete MYWORKSPACE/my-service {env-uuid} --confirm
|
|
229
|
+
|
|
230
|
+
# Environment variables (secured values show as <secured>)
|
|
231
|
+
bitbottle environment variable list MYWORKSPACE/my-service {env-uuid}
|
|
232
|
+
bitbottle environment variable set MYWORKSPACE/my-service {env-uuid} DEPLOY_KEY prod-val
|
|
233
|
+
bitbottle environment variable set MYWORKSPACE/my-service {env-uuid} API_TOKEN secret --secured
|
|
234
|
+
bitbottle environment variable delete MYWORKSPACE/my-service {env-uuid} {var-uuid}
|
|
235
|
+
```
|
|
236
|
+
|
|
237
|
+
All commands support `--json fields` and `--jq expr`. Variable `delete` takes
|
|
238
|
+
the variable UUID (not the key) — run `environment variable list --json uuid,key`
|
|
239
|
+
to find it. Secured variable values are never returned by the API once set.
|
|
240
|
+
|
|
241
|
+
These commands return a typed unsupported-capability error on Bitbucket Server /
|
|
242
|
+
Data Center — deployments and environments are a Cloud-only feature.
|
|
243
|
+
|
|
208
244
|
### Webhooks
|
|
209
245
|
|
|
210
246
|
```bash
|