zeabur 0.17.0 → 0.18.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 +35 -0
- package/package.json +1 -1
- package/zeabur_darwin_amd64_v1/zeabur +0 -0
- package/zeabur_darwin_arm64_v8.0/zeabur +0 -0
- package/zeabur_linux_amd64_v1/zeabur +0 -0
- package/zeabur_linux_arm64_v8.0/zeabur +0 -0
- package/zeabur_windows_amd64_v1/zeabur.exe +0 -0
- package/zeabur_windows_arm64_v8.0/zeabur.exe +0 -0
package/README.md
CHANGED
|
@@ -117,6 +117,41 @@ npx zeabur deployment log -t=build --env-id <env-id> --service-name <service-nam
|
|
|
117
117
|
npx zeabur <command> --help
|
|
118
118
|
```
|
|
119
119
|
|
|
120
|
+
## Workspaces (personal / team)
|
|
121
|
+
|
|
122
|
+
By default, the CLI acts under the personal workspace — the account that logged in. To list or create projects under a team you belong to, switch the workspace:
|
|
123
|
+
|
|
124
|
+
```shell
|
|
125
|
+
# show your personal workspace + all teams you belong to, with your role per team
|
|
126
|
+
npx zeabur workspace list
|
|
127
|
+
|
|
128
|
+
# switch to a team — pass either the team name OR its 24-char ObjectID.
|
|
129
|
+
# A 24-char hex value is always interpreted as an ID; anything else is
|
|
130
|
+
# looked up by name. If multiple teams share a name the CLI errors out and
|
|
131
|
+
# prints the per-candidate `workspace switch <id>` invocation so you can
|
|
132
|
+
# pick by ID (team names are unconstrained, so duplicates are possible).
|
|
133
|
+
npx zeabur workspace switch acme
|
|
134
|
+
|
|
135
|
+
# show the workspace the CLI is currently using
|
|
136
|
+
npx zeabur workspace current
|
|
137
|
+
|
|
138
|
+
# return to the personal workspace
|
|
139
|
+
npx zeabur workspace clear
|
|
140
|
+
```
|
|
141
|
+
|
|
142
|
+
Switching a workspace clears the pinned project / environment / service context, because resource IDs do not overlap between workspaces.
|
|
143
|
+
|
|
144
|
+
The workspace only affects directory-level commands (`project list`, `project create`, `deploy` without a linked project). Commands that take a specific service or deployment ID use that resource's own owner and are workspace-independent — your team's `service restart` works the same regardless of which workspace is active.
|
|
145
|
+
|
|
146
|
+
For one-off commands that should run under a different workspace without switching the persisted state, use the `--workspace` flag:
|
|
147
|
+
|
|
148
|
+
```shell
|
|
149
|
+
# list projects in the "acme" team without switching workspaces
|
|
150
|
+
npx zeabur --workspace acme project list
|
|
151
|
+
```
|
|
152
|
+
|
|
153
|
+
`switch personal` is **not** a way to return to personal — it always looks for a team literally named `personal` (team names are unconstrained). Use `workspace clear` to go back.
|
|
154
|
+
|
|
120
155
|
## Development Guide
|
|
121
156
|
|
|
122
157
|
[Development Guide](docs/development_guide.md)
|
package/package.json
CHANGED
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|