12.4 Assignment - Deploying An API Service

Overview

In this assignment, you will be using your web service application created in the 12.3 assignment and preparing it for deployment, then you will deploy the readied service using FTP and Microsoft Azure.

Work through the stories in order. Use the acceptance criteria to check each feature, and complete the nested tasks using the specified names, values, and scenarios.

Checkpoint reference
Operation	Checkpoint response
GET	200 OK with the requested data.
POST	200 OK with the created result, as required here.
PUT (12.4 onward)	200 OK after the update.
DELETE (12.5)	204 No Content after deletion.

Update a record with PUT

Acceptance Criteria

Acceptance criteria

At least one PUT endpoint updates an existing database row.
A successful update returns HTTP 200.
A follow-up GET confirms the changed values.

Instructions

1.Create at least one PUT request that updates an existing table.

A In the DataService class create a method to update the chosen entity.

B In the API controller create a method that will call the DataService's method to update the chosen entity.

1 Add a PUT attribute that configures the URL to point to that specific API call.

2 Return a new status code result 200

C Check your work in Postman and ensure that the new PUT request works as expected.

Publish and verify the service

Acceptance Criteria

Acceptance criteria

The build script creates the deployment output in dist.
The updated service is deployed in the course Azure environment.
Postman uses the Production environment and domain variable to verify the deployed calls.

Instructions

2.Create a build script to publish your application to a dist folder.

A Create a build script to publish your application to a dist folder.

3.Using MIcrosoft Azure, deploy your updated web service.

A Using MIcrosoft Azure, deploy your updated web service.

4.Check your work in Postman using a Production environment and a global domain variable that points to your deployed web service's URL.

A Check your work in Postman using a Production environment and a global domain variable that points to your deployed web service's URL.

Document and submit the deployed API

Acceptance Criteria

Acceptance criteria

The Word document includes the deployed domain and each API-call URL.
The submission contains a copy of the completed project with node_modules removed.

Instructions

5.Create a Word document that documents the domain name of your deployed application, and the URL of each of the API calls.

A Create a Word document that documents the domain name of your deployed application, and the URL of each of the API calls.

6.Submit a zipped folder of a copy of your application containing your completed application and the Word document, and with…

Submit a zipped folder of a copy of your application containing your completed application and the Word document, and with the node_modules folder removed.

A Submit a zipped folder of a copy of your application containing your completed application and the Word document, and with…

Submit a zipped folder of a copy of your application containing your completed application and the Word document, and with the node_modules folder removed.

Completion review

7.Review the feature acceptance criteria

A Confirm the required results

Return to each story and verify its acceptance criteria. Preserve the submission format and destination stated in the activity; a reading, setup guide, lab, video demonstration, and oral final may require different evidence.

Update a record with PUT Publish and verify the service Document and submit the deployed API