[FEAT] API End point for delete product for authenticated users

[ugojo]

Description

Develop API endpoint that delete product from database. which restricts the deletion of products to authenticated users only. This is to ensure the security and integrity of our product data.

Endpoint Feature

• This endpoint enables authenticated users to delete product.
• Restricts the deletion of products to authenticated users only.

Acceptance Criteria

• [ ] The endpoint should be accessible at api/v1/products/{id}
• [ ] The endpoint should accept HTTP DELETE requests.
• [ ] The endpoint should be secured to ensure that only authenticated users can delete products.
• [ ] Requests to the endpoint must include a valid authentication token in the Authorization header. Authorization: Bearer

• [ ] Requests to the end point must include product id to be delete

  Request Example DELETE /api/v1/product/{id} Authorization: Bearer

Response Example:

• On a successful delete, the API should return a 204 Status Code.
• The response body should contain message in string format.

 {
   "status": "success",
   "status_code": 204,
   "message": "Product deleted successfully."
 }

Authentication and Authorization:

• Only authenticated users should be able to access this endpoint.
• Users must have the necessary permissions (e.g., admin role) to delete a product.

Implementation Details:

• Implement middleware to check for authentication and authorization before allowing the delete operation.
• Add tests to verify that only authenticated and authorized users can delete products.

Error Handling:

• Ensure clear and user-friendly error messages are displayed for authentication and authorization failures.

• Unauthorized Request, the API should return a 401 Unauthorized Status Code

 {
    "status": "Bad Request",
    "status_code": 401,
    "message": "Authentication required."
 }

• Invalid Product ID, the API should return a 404 Not Found Status Code
• The response should should contain message in string format

 {
     "status": "Not Found",
     "status_code": 404,
     "message": "Product not found."
 }

Performance and Security

Performance Considerations

• Review potential performance implications and optimize the API for efficiency.
• Example: Implement rate limiting to prevent abuse.

Security Concerns:

• Address security considerations such as data sanitization.
  • Example: Ensure proper handling of user data to prevent security breaches.

Documentation

API Documentation:

• Ensure that API documentation is updated to include details about the new endpoint, request/response formats, error handling, and authentication requirements. Technical Notes Include any additional technical notes or considerations.

Testing Requirements

Unit Tests

• Write unit tests to validate that only authenticated and authorized users can delete products. Integration Tests

• Ensure end-to-end functionality is tested with integration tests.

  Dependencies and Impact

  Dependencies

Identify dependencies on other tasks or systems, such as user authentication.

[incredible-phoenix246]

@AdeGneus check this

[AdeGneus]

You wrote an issue for a DELETE endpoint only to add PUT method in the acceptance criteria. The responses should follow this format:

{
"status": "success",
"status_code": 204,
"message": "Product deleted successfully"
}

[AdeGneus]

Ensure that you format the markdown properly

[ugojo]

Ensure that you format the markdown properly

I have implemented the changes , please confirm

[AdeGneus]

@ugojo use checkbox for the acceptance criteria