Database Dictionary Audit for Package:Package
Recently the database team has started documenting all database tables in db/doc
. As an MVP, we've assigned
each table to a feature category. We attempted to automate this, and then made rough guesses on the ones that
couldn't be automatically identified either using this spreadsheet
or just by guessing based on their name and code references. In order to make sure these are accurate, I'm
asking every team to take a look at the tables associated with their feature categories assoicated with their
stages.
What we need from your team? Look through the list of tables and fix any mistaken labels and update the description field to help folks know what purpose the table serves.
Process (per table)
- Are the feature categories correct?
- Keep in mind that tables can have multiple categories. Look at the list and if there are any other categories it belongs to, add them.
- If a table has no category that seems to be a perfect match, assign it to the closest match. Tables must have at least one feature category.
- If the table is assigned to a feature category for a different group, open a merge request changing the category and assign it to the EM for the group responsible for that category.
- Update the description of the table to give anybody interacting with it context around the purpose and submit a merge request with the information.
- Double check the
milestone
andintroduced_by_url
to see if they are accurate
Tables
-
container_expiration_policies -
container_registry is the correct feature category or has been updated -
container_expiration_policies description has been updated -
container_expiration_policies milestone
andintroduced_by_url
seem accurate
-
-
container_repositories -
container_registry is the correct feature category or has been updated -
container_repositories description has been updated -
container_repositories milestone
andintroduced_by_url
seem accurate
-
-
packages_events -
package_registry is the correct feature category or has been updated -
packages_events description has been updated -
packages_events milestone
andintroduced_by_url
seem accurate
-
-
packages_composer_metadata -
package_registry is the correct feature category or has been updated -
packages_composer_metadata description has been updated -
packages_composer_metadata milestone
andintroduced_by_url
seem accurate
-
-
packages_debian_group_distributions -
package_registry is the correct feature category or has been updated -
packages_debian_group_distributions description has been updated -
packages_debian_group_distributions milestone
andintroduced_by_url
seem accurate
-
-
packages_composer_cache_files -
package_registry is the correct feature category or has been updated -
packages_composer_cache_files description has been updated -
packages_composer_cache_files milestone
andintroduced_by_url
seem accurate
-
-
packages_debian_group_components -
package_registry is the correct feature category or has been updated -
packages_debian_group_components description has been updated -
packages_debian_group_components milestone
andintroduced_by_url
seem accurate
-
-
packages_rubygems_metadata -
package_registry is the correct feature category or has been updated -
packages_rubygems_metadata description has been updated -
packages_rubygems_metadata milestone
andintroduced_by_url
seem accurate
-
-
packages_debian_project_distributions -
package_registry is the correct feature category or has been updated -
packages_debian_project_distributions description has been updated -
packages_debian_project_distributions milestone
andintroduced_by_url
seem accurate
-
-
packages_maven_metadata -
package_registry is the correct feature category or has been updated -
packages_maven_metadata description has been updated -
packages_maven_metadata milestone
andintroduced_by_url
seem accurate
-
-
packages_debian_project_distribution_keys -
package_registry is the correct feature category or has been updated -
packages_debian_project_distribution_keys description has been updated -
packages_debian_project_distribution_keys milestone
andintroduced_by_url
seem accurate
-
-
namespace_package_settings -
package_registry is the correct feature category or has been updated -
namespace_package_settings description has been updated -
namespace_package_settings milestone
andintroduced_by_url
seem accurate
-
-
packages_pypi_metadata -
package_registry is the correct feature category or has been updated -
packages_pypi_metadata description has been updated -
packages_pypi_metadata milestone
andintroduced_by_url
seem accurate
-
-
packages_dependency_links -
package_registry is the correct feature category or has been updated -
packages_dependency_links description has been updated -
packages_dependency_links milestone
andintroduced_by_url
seem accurate
-
-
packages_nuget_dependency_link_metadata -
package_registry is the correct feature category or has been updated -
packages_nuget_dependency_link_metadata description has been updated -
packages_nuget_dependency_link_metadata milestone
andintroduced_by_url
seem accurate
-
-
packages_packages -
package_registry is the correct feature category or has been updated -
packages_packages description has been updated -
packages_packages milestone
andintroduced_by_url
seem accurate
-
-
packages_debian_group_distribution_keys -
package_registry is the correct feature category or has been updated -
packages_debian_group_distribution_keys description has been updated -
packages_debian_group_distribution_keys milestone
andintroduced_by_url
seem accurate
-
-
packages_conan_file_metadata -
package_registry is the correct feature category or has been updated -
packages_conan_file_metadata description has been updated -
packages_conan_file_metadata milestone
andintroduced_by_url
seem accurate
-
-
packages_conan_metadata -
package_registry is the correct feature category or has been updated -
packages_conan_metadata description has been updated -
packages_conan_metadata milestone
andintroduced_by_url
seem accurate
-
-
packages_package_file_build_infos -
package_registry is the correct feature category or has been updated -
packages_package_file_build_infos description has been updated -
packages_package_file_build_infos milestone
andintroduced_by_url
seem accurate
-
-
packages_debian_group_architectures -
package_registry is the correct feature category or has been updated -
packages_debian_group_architectures description has been updated -
packages_debian_group_architectures milestone
andintroduced_by_url
seem accurate
-
-
packages_tags -
package_registry is the correct feature category or has been updated -
packages_tags description has been updated -
packages_tags milestone
andintroduced_by_url
seem accurate
-
-
packages_dependencies -
package_registry is the correct feature category or has been updated -
packages_dependencies description has been updated -
packages_dependencies milestone
andintroduced_by_url
seem accurate
-
-
packages_debian_project_architectures -
package_registry is the correct feature category or has been updated -
packages_debian_project_architectures description has been updated -
packages_debian_project_architectures milestone
andintroduced_by_url
seem accurate
-
-
packages_debian_project_components -
package_registry is the correct feature category or has been updated -
packages_debian_project_components description has been updated -
packages_debian_project_components milestone
andintroduced_by_url
seem accurate
-
-
packages_helm_file_metadata -
package_registry is the correct feature category or has been updated -
packages_helm_file_metadata description has been updated -
packages_helm_file_metadata milestone
andintroduced_by_url
seem accurate
-
-
packages_debian_file_metadata -
package_registry is the correct feature category or has been updated -
packages_debian_file_metadata description has been updated -
packages_debian_file_metadata milestone
andintroduced_by_url
seem accurate
-
-
packages_nuget_metadata -
package_registry is the correct feature category or has been updated -
packages_nuget_metadata description has been updated -
packages_nuget_metadata milestone
andintroduced_by_url
seem accurate
-
-
packages_debian_publications -
package_registry is the correct feature category or has been updated -
packages_debian_publications description has been updated -
packages_debian_publications milestone
andintroduced_by_url
seem accurate
-
-
packages_debian_project_component_files -
package_registry is the correct feature category or has been updated -
packages_debian_project_component_files description has been updated -
packages_debian_project_component_files milestone
andintroduced_by_url
seem accurate
-
-
packages_build_infos -
package_registry is the correct feature category or has been updated -
packages_build_infos description has been updated -
packages_build_infos milestone
andintroduced_by_url
seem accurate
-
-
packages_package_files -
package_registry is the correct feature category or has been updated -
packages_package_files description has been updated -
packages_package_files milestone
andintroduced_by_url
seem accurate
-
-
packages_debian_group_component_files -
package_registry is the correct feature category or has been updated -
packages_debian_group_component_files description has been updated -
packages_debian_group_component_files milestone
andintroduced_by_url
seem accurate
-
-
packages_npm_metadata -
package_registry is the correct feature category or has been updated -
packages_npm_metadata description has been updated -
packages_npm_metadata milestone
andintroduced_by_url
seem accurate
-
-
dependency_proxy_image_ttl_group_policies -
dependency_proxy is the correct feature category or has been updated -
dependency_proxy_image_ttl_group_policies description has been updated -
dependency_proxy_image_ttl_group_policies milestone
andintroduced_by_url
seem accurate
-
-
dependency_proxy_group_settings -
dependency_proxy is the correct feature category or has been updated -
dependency_proxy_group_settings description has been updated -
dependency_proxy_group_settings milestone
andintroduced_by_url
seem accurate
-
-
dependency_proxy_manifests -
dependency_proxy is the correct feature category or has been updated -
dependency_proxy_manifests description has been updated -
dependency_proxy_manifests milestone
andintroduced_by_url
seem accurate
-
-
dependency_proxy_blobs -
dependency_proxy is the correct feature category or has been updated -
dependency_proxy_blobs description has been updated -
dependency_proxy_blobs milestone
andintroduced_by_url
seem accurate
-
-
lfs_object_states -
git_lfs is the correct feature category or has been updated -
lfs_object_states description has been updated -
lfs_object_states milestone
andintroduced_by_url
seem accurate
-
-
lfs_objects -
git_lfs is the correct feature category or has been updated -
lfs_objects description has been updated -
lfs_objects milestone
andintroduced_by_url
seem accurate
-
-
lfs_objects_projects -
git_lfs is the correct feature category or has been updated -
lfs_objects_projects description has been updated -
lfs_objects_projects milestone
andintroduced_by_url
seem accurate
-
-
lfs_file_locks -
git_lfs is the correct feature category or has been updated -
lfs_file_locks description has been updated -
lfs_file_locks milestone
andintroduced_by_url
seem accurate
-
Why is this effort happening?
There have been many times that issues occur in production, but the the infrastructure team doesn't have the information it needs to identify subject matter experts who can help resolve things quickly. This in turn can delay the time it takes to find and fix pressing issues.
How much time should we expect to spend on this?
Depends, if the team has a lot of tables, it may take a little bit to get all of the information together. If not, this could be very fast. The descriptions are as much or little as the team wants to add. More information may help folks self service better.
How urgent is this?
The urgency is up to the team. If the tables have poor information or are misassigned, that may cause more burden on the team when answering questions.