airyhq / airy Goto Github PK

As a core user
I want to be able to reset password for a specific user
So the password is changed

POST /users.password-reset
{
  "token": "a valid request password token",
  "new_password": "a valid new password"
}

Returns

200 OK {}

As a core auth user
I want to be able to send email

We need to allow core users to configure email providers
For the MVP we could use ENV variables to configure SMTP

POST /users.login
{
  "id": "user-id",
  "password": "<pass>"
}

Returns

{
  "id": "424242-4242-42-4242-4242",
  "first_name": "Grace",
  "last_name": "Hopper",
  "token": "JWT_TOKEN"
}

The returned JWT token must have the user_id on the payload

Allow users to connect chat plugin channels in the admin app.

When I have already a registered user
And I hit the /users.signup endpoint with the same email
I get a 500 error

Expected behaviour: The returned status should be 403

Both in the core and on platform we have two types of apps with health check endpoints:

Some use an explicitly defined endpoint at /health, while others implicitly use the Spring provided /actuator/health.

Run the current state locally and check if ingestion works and APIs work

Have a loook at docs/self-source/ and see what we can keep/discard for the OSS version.

• Move api/worker/webhook-publisher and use interactive queries
• Move api/worker/redis-worker
• Move webhook admin code to admin app

Allow authenticated anonymous web users to send and receive messages.

In order to be able to send structured webhooks we need an mvp of the mapping library to be able to render Facebook text messages.

Publish library with basic ui components in order everyone can use it

Attribute springboot.bzl original work

We want to be able to start all core apps from a single JAR

Review topics config configuration

As a logged user
I want to the private airy endpoints on core to verify my identity
So that other users don't access it

Our webhooks need an in-cluster redis installation that they can use for the queueing. Therefore the bootstrap should create one.

Move work in progress from zube to github projects

Core Auth app needs to serve signups as an endpoint

POST /users.signup
{
  "email": "[email protected]",
  "first_name": "Grace",
  "last_name": "Hopper",
  "password": "much-password-such-sec"
}

Returns

{
  "id": "11111111-2222-3333-4444-5555555555555",
  "created_at": "2016-05-15T19:53:12.368652374-07:00",
  "updated_at": "2016-05-15T19:53:12.368652374-07:00",
  "token": "JWT_TOKEN"
}

Summary

• GIVEN I have configured the Facebook App Id, App Secret and Webhook Secret in the config file /infrastructure/airy.conf
• GIVEN I have run vagrant provision --provision-with user-data
• GIVEN I have a valid auth token
• WHEN I send an authenticated request to /channels.connect with the required parameters being defined
• THEN I receive a 500 error with error message

{
  "message": "400 Bad Request: [{\"error\":{\"message\":\"Invalid Client ID\",\"type\":\"OAuthException\",\"code\":101,\"fbtrace_id\":\"A9Wfm-HkGSKuWvJYetcjDY_\"}}]"
}

URL:

https://github.com/airyhq/core/blob/main/docs/api.md#connecting-channels

Steps to reproduce:

Send an authenticated request such as:

curl --request POST \
  --url http://192.168.50.5:20947/channels.connect \
  --header 'authorization: SOME_VALID_TOKEN' \
  --header 'content-type: application/json' \
  --data '{
	"source": "facebook",
	"source_channel_id": "SOME_PAGE_ID",
	"token": "SOME_VALID_FACEBOOK_USER_TOKEN"
}'

Actual result:

500 Error - indicating that the relevant Airy App ID and App Secret where not applied correctly to the relevant request to Facebook

Expected result:

The relevant Facebook Page should be connected

Environment:

Local

Severity/Priority:

High/High

Reproducible:

Multiple times

Browsers:

Platform/OS:

MacBook Pro 16GB RAM

Date & Time:

22.10.2020 at 11:07 UTC

Reporter:

steffh

Attachments:

Notes:

Create showcase app to display the components in the library

• Make it work with Bazel
• Deploy it on components.airy.co or docs.airy.co/components

Currently we are packaging the Airy Core Platform on an existing CentOS image and in order to make the whole package smaller, we need to user either Debian or some other alternative, to make it as slim as possible, but still to run with all the features and functionalities.

Implement what is now known as the /login-via-app endpoint and the websocket handshake for clients.

Make sure the endpoints follow the convention /something.action

Userstory

As an open-source developer using the core platform
I want to start the core on minikube
so that I can have the setup locally

Acceptance Criteria

• GIVEN I have the core repository locally
• WHEN I run a certain command
• THEN I have a minimum facebook ingestion platform
• THEN I have an admin service for adding/removing channels
• THEN I have a minimum message and conversation API

Dev Notes

Definition of Done

• Code review done
• Acceptance criteria passed
• Documentation done
• Internal rollout communication done

As a core user
I want to request a password reset for an email
So the user receives a reset password email

POST /users.request-password-reset
{
  "email": "[email protected]"
}

Returns a 200 response with an empty body and sends an email containing a valid reset link

endpoints:

• channels.connected
• channels.available
• channels.connect
• channels.disconnect

Before we can actually open source the repository there's a variety of tasks that must be completed:

• Add a license
• Rewrite the kafka cluster test code as it's now a copy and paste from confluent code
• Document the data model accurately
• attribute springboot.bzl original work
• move work in progress from zube to github projects
• Make sure the endpoints follow the convention /something.action
• Review topics config configuration
• Limit the repository's deployment credentials to only the resources it needs

• return on API
• send via websocket
• mark read api

As a core user
I want to click on a accept invitation link that came by email
So that my user gets created

POST  /users.accept-invitation
{
  "id": "invitation-id",
  "first_name": "First name",
  "last_name": "Last name",
  "password": "strong password"
}

returns

{
  "id": "user id",
  "email": "[email protected]",
  "first_name": "First name",
  "last_name": "Last name",
  "token": "TOKEN"
}

At the moment, the script assumes you run it from the top folder of the mono repo

Document the data model accurately

As a user of the core
I want to be able to create open invitations to users
So they can receive invitation emails

POST /create-invitation
{
  "email": "email to invite"
}

Returns 200 with an empty response

The invitee should receive an invitation email

New app that uses JDBI with a simple /hello-world endpoint that returns JSON data

After running scripts/bootstrap.sh

 git status
On branch main
Your branch is up to date with 'origin/main'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   deployments/api-admin.yaml
	modified:   deployments/sources-facebook-events-router.yaml
	modified:   deployments/sources-facebook-webhook.yaml

no changes added to commit (use "git add" and/or "git commit -a")

• message upsert websocker
• docs
• channel websockets

Rewrite the kafka cluster test code as it's now a copy and paste from confluent code