SSWConsulting / SSWConsulting/SSW.Rules

Consolidate SSW Rules Resource Groups in Azure

Open
#1,437 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

01-small Type: DevOps
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
  1. All SSW Rules resources are consolidated into 2 resources in Azure.
  2. The new resource groups are named 'SSW Rules.{{ ENV }}'.
  3. Checked by Warwick - he can easily track costs associated with SSW Rules in Azure
  4. 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
  1. Log in to the Azure portal.
  2. Navigate to the 'Resource groups' section.
  3. 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.