MEFE API - Unit creation

[kaihendry]

We need to know the JSON payloads and the SQL queries itemised step by step.

[franck-boullier]

The lambda generated from the SQL will look like this:

CALL mysql.lambda_asyncarn:aws:lambda:ap-southeast-1:192458993663:function:alambda_simple{"actionType": "CREATE_UNIT", "creatorId": "NXnKGEdEwEvMgWQtG", "name": "SG_SIN_LUM_36-01_05R", "moreInfo": null, "streetAddress": "Lumiere \n #36-01", "city": null, "state": "", "zipCode": null, "country": null, "ownerId": "NXnKGEdEwEvMgWQtG"}

@kaihendry this is most likely missing the id for the record from the origin.
Suggestion: name this unitCreationRequestId

[kaihendry]

I believe I need to POST to POST Create a new unit by MEFE internal API* with MEFE internal API.

An example payload is:

{
	"actionType": "CREATE_UNIT",
	"creatorId": "R4vBD6BZRCNx8JwnM",
	"name": "Unit test 128288",
	"type": "Villa",
	"moreInfo": "lasdl",
	"streetAddress": "asdads",
	"city": "asdasd",
	"state": "",
	"zipCode": "292929",
	"country": "Singapore"
}

So I will check for actionType for posting to /api/process-api-payload othewise it will post by default to /api/db-change-message/process

[nbiton]

An example request and response from MEFE API to a request with an "actionType" of "CREATE_UNIT":

{
	"actionType": "CREATE_UNIT",
	"creatorId": "R4vBD6BZRCNx8JwnM",
	"name": "Unit test 128288",
	"type": "Villa",
	"moreInfo": "lasdl",
	"streetAddress": "asdads",
	"city": "asdasd",
	"state": "",
	"zipCode": "292929",
	"country": "Singapore"
}
{
    "unitMongoId": "m3KTgSW2m1FSLSCnp",
    "timestamp": "2019-03-18T03:37:03.179Z"
}

[franck-boullier]

The SQL that will need to be run to update the SQL after the Unit is created (i.e: the MEFE API Returns a success):

SET @unit_creation_request_id = 'unitCreationRequestId';
SET @mefe_unit_id = 'unitMongoId (from_API_response)';
SET @creation_datetime = 'timestamp (from_API_response)';
CALL ut_creation_success_mefe_unit_id;

[kaihendry]

Time stamp is just a string right? No special sql Type?

No environment variables, right?

[franck-boullier]

Time stamp is just a string right? No special sql Type?

Timestamp is SQL datetime

No environment variables, right?

Not in v1.0

[kaihendry]

@franck-boullier I'm getting Error 1305: PROCEDURE bugzilla.ut_creation_success_mefe_unit_id does not exist in the dev environment.

[nbiton]

timestamp is an iso string date format (in the API response)

[franck-boullier]

In order to capture the information 'was this unit there in Unee-T before or not?' we need to change the SQL as such:

• IF API returns 200

SET @unit_creation_request_id = 'unitCreationRequestId';
SET @mefe_unit_id = 'unitMongoId (from_API_response)';
SET @creation_datetime = 'timestamp (from_API_response)';
SET @is_created_by_me = 0;
CALL ut_creation_success_mefe_unit_id;

• IF API returns 201

SET @unit_creation_request_id = 'unitCreationRequestId';
SET @mefe_unit_id = 'unitMongoId (from_API_response)';
SET @creation_datetime = 'timestamp (from_API_response)';
SET @is_created_by_me = 1;
CALL ut_creation_success_mefe_unit_id;

[kaihendry]

Still the "Error 1305: PROCEDURE bugzilla.ut_creation_success_mefe_unit_id does not exist" issue.