microsoft / microsoft/AzureTRE

Include 3rd party solutions like CycleCloud in cost reporting

Open
#2,955 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

story
Dominant language
Python
Stars
235
Forks
192
Avg merge
1d 23h
Merged PRs (30d)
13

Description

Description

As a TRE Administrator and TRE Workspace Owner
I want to see costs for 3rd party solutions like CycleCloud costs etc.,
So that I would know how much it cost.

Acceptance criteria

  • Resources by 3rd party solutions and other first party services like Databricks clusters roll up in cost reporting

Technical notes

Cost reporting has functionality for rolling up untagged cost assuming that those resources are deployed in a cost-tagged resource group and api-app identity has reader permissions to that resource group (#2610).
In this story we need to explore what is needed to do so with least privilege access (not giving a subscription level reader role),
for solutions like CycleCloud,
For instance, pre-deploy resource group with cost tags and reader role assignment and then deploy the solution into that resource group.

Contributor guide

Open the contributing guide

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 with the existing cost-reporting roll-up functionality described in issue #2610, then examine how CycleCloud and Databricks resources are deployed into resource groups. Investigate the least-privilege reader access needed for these resources. Done means third-party and first-party solution costs appear in cost reporting without requiring subscription-level reader access.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
backend, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.