microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Chores for undeprecating AksSamples
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
- Update chart yamls to support currently GA supported k8s version
- Update usage of dependency charts, like ingress-nginx and cert-manager
- Update Dockerfile to using Windows Server 2022 (current default for deploying nodes in AKS)
- Update to
.NET 6.NET 8 :) - Update nuget dependencies
- Restructure code to adhere to new paradigms coming with .NET 6, such as replacing singleton pattern with dependency injection, changes to web host creation and similar
- Update docs for provisioning and deployment
- Add Actions workflow CI for build validation and unit test runs
- Remove
(Deprecated)folder name suffix - (Remove useless ghost docs?)
@samarthasthana My company is currently evaluating to do these steps for the eco-system. If they decide to go with it and providing we deliver same or higher quality than the current sample, would you be open for merging our efforts into this repo? This would also resolve the numerous auto PRs from dependabot that are currently open.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the AksSamples area and the completed checklist in this issue; no specific files, tests, or entry points are named. Confirm whether the listed modernization work is still needed, then use the checklist as the definition of done for the .NET, AKS, dependency, documentation, CI, and naming updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, docker, github-actions, kubernetes
- Domain
- ci-cd, cloud, devops, documentation, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100