App
access_key()
The Access Key from the environment, or an error explaining where to get one.
Source code in dynamiq/cli/commands/app.py
22 23 24 25 26 27 28 29 30 | |
app_connect_token(*, api, settings, app_id, user_id, requirement_ids)
Mint a CONNECT LINK for ONE end user so they attach their own accounts.
Give the returned url to that person and nobody else: it is scoped to them and this app,
and expires after 24 hours. Never open or reuse it yourself. Scope it with --requirement
for a per-integration "Connect" button.
This is NOT integration connect-project, which connects YOUR project's shared account.
Sending that one to an end user looks like it worked and leaves the run unsatisfied,
because nothing ties the account to them or to the requirement.
Source code in dynamiq/cli/commands/app.py
269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 | |
app_disconnect(*, api, settings, app_id, requirement_id, user_id)
Delete ONE end user's connected account for a requirement; they must connect it again to use it.
Source code in dynamiq/cli/commands/app.py
298 299 300 301 302 303 304 305 306 307 | |
app_endpoint(api, app_id)
Base URL of the deployed app, asked for rather than guessed.
Source code in dynamiq/cli/commands/app.py
33 34 35 36 37 38 39 40 41 42 43 | |
app_requirements(*, api, settings, app_id)
What this app needs each end user to connect, with the titles they will read.
Source code in dynamiq/cli/commands/app.py
246 247 248 249 250 251 | |
app_requirements_status(*, api, settings, app_id, user_id)
Whether ONE end user has connected everything required, and what is still unsatisfied.
Poll this after sending them a connect link. A run for a user with a required requirement unsatisfied fails before the workflow is even built; an unsatisfied optional one only removes the agent tools that need it.
Source code in dynamiq/cli/commands/app.py
254 255 256 257 258 259 260 261 262 263 264 265 266 | |
call_app(url, key, *, method='POST', json_body=None)
Call the app hostname and print the body; non-2xx becomes a readable error.
Source code in dynamiq/cli/commands/app.py
46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 | |
delete_app(*, api, settings, app_id)
Delete an app permanently (its triggers go with it).
Source code in dynamiq/cli/commands/app.py
237 238 239 240 241 242 243 | |
deploy_app(*, api, settings, name, workflow_id, workflow_version_id, description, access, deployment_type, runtime_id, autoscaling)
Create AND deploy an app from a workflow - this is how a workflow becomes callable.
REQUIRED by the API: name, project_id (auto), workflow_id. The call is
synchronous: the response already carries the app id and its hostname.
dynamiq app deploy --name qna --workflow <workflow_id>
A trigger needs an app id, so deploy before dynamiq trigger create.
Source code in dynamiq/cli/commands/app.py
100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 | |
get_app(*, api, settings, app_id)
Fetch one app, including its hostname - the endpoint you call to run it.
Source code in dynamiq/cli/commands/app.py
92 93 94 95 96 97 | |
invoke_app(*, api, settings, app_id, input_data)
Run a deployed app by POSTing to its own hostname - the way an integration calls it.
INPUT_DATA is inline JSON or @file - your Input node's fields, e.g. '{"input": "hi"}'
for an Input node with one field named input. It is wrapped as {"input": {...}}
unless you already pass the envelope, i.e. an object whose input is itself an object.
The hostname is read from GET /v1/apps/{app_id} and authenticated with an Access Key
from the DYNAMIQ_ACCESS_KEY environment variable (create one in the UI; the management
PAT is not accepted there). This is the endpoint the app actually serves - the
management API's /v1/apps/{id}/invoke reverse-proxies through synapse and can fail
while the app itself is healthy, so it is not used.
Source code in dynamiq/cli/commands/app.py
201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 | |
list_apps(*, api, settings, workflow_id, include_archived, page, page_size, fetch_all, compact)
List apps in the current project (25 per page; --all for every one).
Source code in dynamiq/cli/commands/app.py
67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 | |
list_deployments(*, api, settings, app_id)
Deployment history for an app - check here when a deploy looks stuck.
Source code in dynamiq/cli/commands/app.py
229 230 231 232 233 234 | |
redeploy_app(*, api, settings, app_id, workflow_id, workflow_version_id, runtime_id)
Push a new workflow version onto an EXISTING app (keeps its id and hostname).
Use this instead of deploy when the app already exists - workflow_id is required.
Source code in dynamiq/cli/commands/app.py
174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 | |