SSWConsulting / SSWConsulting/SSW.Rules
Consolidate SSW Rules Resource Groups in Azure
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
From YakShaver
https://www.sswyakshaver.com/
cc: @leahy268, Ulysses Maclaren, @adamcogan, @calumjs
Hi Team!
Video: Link
Pain
There are currently three separate resource groups for SSW Rules in the Azure portal: 'SSW rule', 'SSW rules', and 'SSW rules staging'. This is causing confusion and making it difficult for Warwick to track costs. The resource groups should be consolidated into a 2 resources (Staging and Prod) to simplify cost tracking and management.
Acceptance Criteria
- All SSW Rules resources are consolidated into 2 resources in Azure.
- The new resource groups are named 'SSW Rules.{{ ENV }}'.
- Checked by Warwick - he can easily track costs associated with SSW Rules in Azure
- No resources are lost or misconfigured during the consolidation process.
follow
https://www.ssw.com.au/rules/do-you-have-separate-development-testing-and-production-environments/
Reproduce Steps
- Log in to the Azure portal.
- Navigate to the 'Resource groups' section.
- Observe the presence of three separate resource groups: 'SSW rule', 'SSW rules', and 'SSW rules staging'.
Requested by: @bradystroud
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 in the Azure portal by inventorying the three resource groups named in the issue and the resources they contain. Consolidate them into the two requested SSW Rules.{{ ENV }} groups, then verify that no resources are lost or misconfigured and have Warwick confirm that cost tracking is clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100