STORY: Create workspaces API resource collection

Workspaces are created, updated, retrieved and deleted through the /workspaces resource collection on the API.

• Expose resource collection from HTTP API.
• CRUD operations for workspaces based on defined data model
• Resource state stored in state store
• Initialize required Cosmos containers and data.

Acceptance critiera

• Bootstrap cosmos db with /workspaces container #111
• Workspaces resource collection exposed in api
• Workspaces persisted, and retrieved from State store
  • [GET] /workspaces - returns all resource documents that are not marked as deleted #114
  • [POST] /workspaces - creates a resource document in the state store #112
  • [GET] /workspaces/{workspace_id} - returns the given resource document from the state store #113

[christoferlof]

@christoferlof @Lybecker - I updated the acceptance criteria

[GET] /worksapces - returns all resource documents that are not marked as deleted - can you verify if my understanding here is correct, or should it return all?

@TessFerrandez correct, only return workspaces that are not marked as deleted.

[christoferlof]

@christoferlof and @Lybecker - we currently don’t have a physical data model, do we need to create one, or can we use a minimal assumed set for this story, and then incrementally add as we need?

@TessFerrandez minimal assumed set for this story please, and then we add as we need. Should be aligned with the logical data model though.