Task 9: point frontend to Elastic Beanstalk cart API

[nextsukhorutchenko]

What was done?

Updated frontend Cart Service placeholder for Task 9.

Frontend scope

• Replaced the Cart Service placeholder in src/constants/apiPaths.ts with the planned Elastic Beanstalk Cart API URL:

http://nextsukhorutchenko-cart-api-prod.eu-west-1.elasticbeanstalk.com

• Existing cart/order query code already calls Cart Service routes from Task 8:
  • GET /api/profile/cart
  • PUT /api/profile/cart
  • GET /api/profile/cart/order
  • PUT /api/profile/cart/order

Links for review

• Frontend PR: Task 9: point frontend to Elastic Beanstalk cart API #7
• Backend PR: Task 9: containerize cart service for Elastic Beanstalk aws-shop-backend#6
• Planned Cart Service API URL: http://nextsukhorutchenko-cart-api-prod.eu-west-1.elasticbeanstalk.com
• Current frontend deployment: https://ddiqx6yb3n1i1.cloudfront.net/
• Existing Product Service API: https://5y1h93nifb.execute-api.eu-west-1.amazonaws.com/prod/products
• Existing Import Service API: https://qsutnud80j.execute-api.eu-west-1.amazonaws.com/prod/import

Verification flow after EB deploy

1. Create/deploy backend EB environment with CNAME nextsukhorutchenko-cart-api-prod.
2. Open frontend.
3. Login/register to get Basic auth token in localStorage.
4. Add/remove items from products page.
5. Verify requests go to Cart Service EB URL.
6. Refresh page and verify cart state is loaded from Cart Service database.

Validation

Passed locally:

• npm run build

Vite emitted existing dependency warnings and bundle-size warning, but build completed successfully.

Notes

The EB URL is planned and will become active after eb create prod --cname nextsukhorutchenko-cart-api-prod --single --envvars ... is run with real RDS env vars.