Skip to content

As a developer, I can configure and deploy Azure App Service #60

Closed
@James-Nance

Description

@James-Nance

Description

As a developer, I can configure and deploy Azure App Service

For Cobalt, App Service should provide:

  • App/container hosting
  • Public IP mapped to container port (Dependency on Julio Research)
  • Load balancing (Another User story for scale out config)

Acceptance Criteria

Reference: [Done-Done Checklist] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/DoneDone.md)

  • Service plan is already deployed before starting deployment of app service

  • Key value pair for app service name and linux fx version

  • open question: service aplan module depends on app service

  • [ ]Output in readme with an example output

  • VNET is an option for App Service. (No data block needed)

  • No hardcoded variables in module config; everything set through Terraform template

  • Usage referenced in Azure Simple template

  • Screenshot showing resource provisioned in Azure Portal

Also, here are a few points that need to be addressed:

  1. No hardcoded variables in module config; everything set through Terraform template

Resources

Tasks

Stories are intended to be completed in a single sprint; if task breakdown creates addition work then team should discuss promoting the Story to an Epic.
Reference: [Minimal Valuable Slices] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/MinimalSlices.md)

Reference: [How to Write Better Tasks] (http://agilebutpragmatic.blogspot.com/2012/04/splitting-story-into-tasks-how-to-write.html)

Assignee should break down work into tasks here

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions