[EXAMPLE TECH DEBT ITEM] No cloud budget controls

[olitomlinson]

Tech Debt acceptance criteria

• Products & Platforms affected have been identified - labels applied (chat, platform etc)
• Impacted characteristics have been identified - labels applied (security, availability, CI/CD etc)
• Description is completed
• Recommend actions have been defined
• 'Payback' trigger points have been identified

Description

We currently have no cloud budgets in place which means we have a significant liability that is unchecked.

What is it?

Cloud budgets are essential to reducing the likelihood of receiving an unexpected budget at the next billing cycle.

Our liability is in the thousands, so this could be extremely significant.

Probability of being impacted

Very likely

Negatively impacted characteristics

• Cost
• Our credibility

What specific/domains resources, if any, are affected

Everything in the dev and prod subscriptions.

Expected vs actual behavior

N/A

Repro steps

N/A

Framework / Runtime versions which may be relevant

N/A

Recommended Action

What is the remediation

Use terraform to apply some basic budgets. they don't have to be 100% accurate, something is better than anything.

Urgency of remediation

Super urgent - i.e. next sprint, or sooner if we can escalate

Effort estimate of remediations

3-5 points

External dependencies requiring co-ordination

Inform Cloud Ops

Payback trigger points

There are no trigger points on this, it just needs doing asap. A trigger point means the issue has already happened and we've missed the boat.

[olitomlinson]

Everyone has reviewed this is the triage session. Happy that this is prioritised into the next sprint.