Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cost Optimization Workbook / Add a new tab for change log #1192

Open
2 tasks
arthurclares opened this issue Dec 6, 2024 · 1 comment · May be fixed by #1207
Open
2 tasks

Cost Optimization Workbook / Add a new tab for change log #1192

arthurclares opened this issue Dec 6, 2024 · 1 comment · May be fixed by #1207
Assignees
Labels
Status: ✍️ Spec in progress Detailed spec is currently in progress Tool: Optimization workbook Cost optimization workbook Tool: Workbooks Azure Monitor workbooks Type: Feature 💎 Idea to improve the product

Comments

@arthurclares
Copy link
Collaborator

📝 Scenario

Users should be able to tell what are the new COW queries.

💎 Solution

Add a new "Change Log" tab under the Overview main tab.

📋 Tasks

Required tasks

Preview Give feedback

Stretch goals

Preview Give feedback

ℹ️ Additional context

🙋‍♀️ Ask for the community

We could use your help:

  1. Please vote this issue up (👍) to prioritize it.
  2. Leave comments to help us solidify the vision.
@arthurclares arthurclares added Tool: Optimization workbook Cost optimization workbook Tool: Workbooks Azure Monitor workbooks Type: Feature 💎 Idea to improve the product labels Dec 6, 2024
@arthurclares arthurclares added this to the 2024-12 - December milestone Dec 6, 2024
@arthurclares arthurclares self-assigned this Dec 6, 2024
@arthurclares arthurclares added the Status: ✍️ Spec in progress Detailed spec is currently in progress label Dec 6, 2024
@flanakin
Copy link
Collaborator

flanakin commented Dec 6, 2024

@arthurclares Is there a way we can reuse or enhance the current changelog to support this without duplicating things?

There are probably more ways, but my initial thoughts are:

  1. Add a filter to the changelog to filter down to one or more tools
  2. Add a build step to generate a tool-specific changelogs from the current changelog
  3. Pull in the changelog via an API call

The first assumes we're okay to link out to a changelog rather than including it in the workbook itself. I feel like that would be better because it'll also let people know what they don't have if they've deployed an older version. Either that or dynamically pull it in (3rd option).

@arthurclares arthurclares linked a pull request Dec 13, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: ✍️ Spec in progress Detailed spec is currently in progress Tool: Optimization workbook Cost optimization workbook Tool: Workbooks Azure Monitor workbooks Type: Feature 💎 Idea to improve the product
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants