Skip to content

Conversation

@garath
Copy link
Member

@garath garath commented Sep 28, 2022

This adds a one-pager for the "Vestigial Objects" effort planned as part of dotnet/dnceng#1274.

Closes #10374.

@garath garath self-assigned this Sep 28, 2022
Copy link
Member

@MattGal MattGal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great. Could it get a bit more crisp on the tasks and maybe SWAG out their costs too?

@@ -0,0 +1,118 @@
# "Vestigal objects" one-pager
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Spelling (Vestigial). Feel free to use some other term for this too, of course.


Azure allows "Tags", which are simply key-value pairs, to be arbitrarily associated with almost any resource. Internally, Microsoft already uses this feature to track assets and configuration across subscriptions (e.g., AzSecPack, NRMSException). "Inventory" is an explicit use case supported in Azure.

This effort will develop a set of standard Tags that will be applied to resources. These Tags will identify, at minimum, resources that are necessary for operation of our services.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do the tags get applied to the resources?

- [ ] Evaluate including Key Vault auditing information
- [ ] Develop Dashboards presenting data to expected audience. Consider Grafana and Power BI (or a mix of both).
- [ ] FR can quickly view changes to an arbitrary resource
- [ ] New resources or resources with an unknown purpose are easily identifiable
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe a nitpick but many of these tasks like "resources are easily identifiable" sound like goals.... consider separating them so we can think more easily about costing.

@garath garath merged commit b036295 into dotnet:main Oct 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Write one-pager for "Manage Vestigial Objects" effort

3 participants