User Story

As a cost management developer, I want to create basic Django scaffolding for Forecasting, so that the codebase has the basic structures in place for delivering GCP cost forecasts.

UX Requirements

• Is there design required for this story?

No.

UI Requirements

• Does the UI require a API contract with the backend so that UI could be developed prior to completing the API work?

Yes. This story will help in creating that contract.

Documentation Requirements

• What documentation is required to complete this story?

Only APIDocs

Backend Requirements

Endpoints

The API response returned should follow the standard paginated response pattern for cost management and Insights applications

• Respect filter/limit paginaton
• links
• meta with count
• data

As a starting point the forecast can always be for all of the current month, so time filter parameters should not be necessary.

We will need API endpoints for the following

• /forecasts/gcp/costs/
• /forecasts/openshift/infrastructures/gcp/costs/
• /forecasts/openshift/infrastructures/all/costs/ (updated to include GCP)

Serializer

• We should not support group by parameters
• We want the filter parameter to support only RBAC filterable values.

AWS

• account
• org unit id

Azure

• subscription guid

OpenShift

• cluster
• node
• project

QE Requirements

• Does QE need to complete specific work for this user story?

No.

Additional Information and Assumptions

• This issue does not require that the Forecast endpoint is returning actual calculated forecasts.
• This issue should implement the serializers, parameter validation, and API endpoints that we expect to use for delivering forecast results.