Azure-Samples/oidc-client-app-service

Add ARM/Bicep deployment strategy

Open

#4 opened on Apr 13, 2022

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)HCL (1 fork)auto 404
documentationgood first issuehelp wanted

Repository metrics

Stars
 (3 stars)
PR merge metrics
 (PR metrics pending)

Description

This sample project currently only has a Terraform deployment strategy. Ideally, there would be a Bicep (or a pure ARM template) deployment.

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

N/A

Any log messages given by the failure

N/A

Expected/desired behavior

N/A

OS and Version?

N/A

Versions

0.2.0

Mention any other details that might be useful

N/A

Contributor guide

Research direction
Study the existing Terraform configurations in the repository to understand the deployed resources: Azure App Service, Azure Container Registry, Azure AD OIDC setup. Then write equivalent Bicep files to deploy the same infrastructure. Compare Terraform and Bicep syntax to translate modules. Test deployment using Azure CLI or VS Code Bicep extension.
Tech stack
terraformazurenodejsdocker
Domain
devopsinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
AzureGitTerraform
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35