Feature/team1/Issue71/completeAzureUsersUserIdFunction

[theKunte]

Resolves Task/BUG :#71

To Test API function users/{userId}

Test this function on Azure:

• API call - users/2

This code completes the implementation of the Azure function for the previous PR #49 that is already merged into the dev branch

• The following methods got implemented and Updated: GET/POST/PUT/PATCH/DELETE

• Once this PR gets approved the function will be deployed automatically into the development branch

• To test this feature locally make sure to have the following:

  • Azure function extension for VSCode
  • Pull the branch to your machine and make sure to be on the correct branch
  • Install the ODBC driver so you can connect to the database: For any issues with the ODBC driver checkout PR49 for additional documentation to fix ODBC driver
    -In local.settings.json at the root of the functions folder, enter in the values for the keys below in the following format: { "Values": { "KEY": "VALUE" } }
    ENV_DATABASE_NAME (name of the database)
    ENV_DATABASE_PASSWORD
    ENV_DATABASE_SERVER (this is the server location)
    ENV_DATABASE_USERNAME

• You can click F5 or click run->Start Debugging in the functions folder to start it up

• The GET request takes the userId and returns all a specific user by their Id.

• The POST request is not allowed for this call.

• The PUT request takes a JSON object { "firstName": "add your firstname", "lastName": "add your last name", "email": "[email protected]" } and will update the user firstName, lastName, email when you select a specific userId.

• The DELETE request takes the userId and deletes the user from the database.
  -To test using JSON, copy the link provided by the debugger (the "/users/{userId}" ) into Postman, and use as usual for GET and PUT (info goes into the body), DELETE (userId). PUT and PATCH are not allowed

• Error handling and Debug handling included in this feature

DATE	ACTIVITY	TIME
1/21	Review PR49 after class to get an idea of what I need to update	1 hr
1/23	More research of pyodbc Crud functionality	1.5 hr
1/24	encounter issue with running function locally	3 hr
1/24	Still figuring out what was going on with the issue	1 hr
1/24	Started working on functionality	1 hr
1/25	Setup all rest methods (get, post, put, delete) to work as expected	2 hr
1/26	Added error handling to post requests and added storage account to function app on azure	2 hr
1/28	Setup all rest methods (get, post, put, delete, patch) to work as expected	1 hr
1/28	wrote this PR which I will have to update again	1 hr
1/31	deployed all function to azure test work fine updated PR	1 hr

[lbrown51]

A general comment is that we probably don't want any of the react code in this PR. Maybe you just need to update from upstream/development?

[jak-ashuraliev]

Since I cannot actually run the functions on my local machine, I can only make comments. Overall, good logging implementation!

[farhadbahrehmandhenry]

not sure if this is necessary, because if there is no id, it basically triggers "/users" endpoint. if you test it without id you'll notice it.

[theKunte]

Yup! You are right. I removed this part since it is not necessary

[farhadbahrehmandhenry]

I just noticed merging you branch will cause deleting the react app from NSC repo, we need to update you branch with NSC first.

[farhadbahrehmandhenry]

tested, all the functionalities are working, good to merge.