-
Currently `/messages.send` only takes in `text` messages.
To support the existing outbound content model and source templates, we need to update the send message API so that the request payload cap…
-
We need a new endpoint `/metadata.upsert` that takes a `subject` (conversation | message | channel) and a `data` object.
`POST /metadata.upsert`
```json5
{
"subject": "conversation|message|c…
-
### Summary
The following criteria must be met for each suggested reply to be eligible to be rendered:
- ID
- name
- source type (This is necessary because we have to know for which source they …
-
As a developer receiving a message from a Facebook user who messaged a Facebook page that is validly connected as a channel of source type "facebook",
in case the tuple of a Facebook page id and a pa…
-
In the sound design document for this sim @Ashton-Morris suggested temporarily using the grab/release sounds that were used for the magnet in "Faraday's Law" as the sounds for picking up and release o…
-
On my machine with the latest vagrant I see this output when running the `bootstrap.sh` script:
```
airy-core: Running: inline script
airy-core: Error from server (Forbidden): pods "star…
-
Provisioning fails with
```
Error: ConfigMap in version "v1" cannot be handled as a ConfigMap: v1.ConfigMap.Data: ReadString: expects " or n, but found 1, error found in #10 byte of ...|RVAL_MS":100…
-
Source specific endpoints currently lack a common collection/domain which is why they are spread out across the documentation in several places despite being HTTP API endpoints all related to channels…
-
We need to review how we inject variables into our configmaps and secrets in the provisioning process and standardize it.
Particularly for these two sed replacements:
https://github.com/airyhq/air…
-
After running the `boostrap` script on `develop` I see this error message:
```
airy-core: The Ingress "airy-core" is invalid:
airy-core: * spec.rules[1].http.paths[0].pathType: Required v…