Skip to content

Database Dictionary Audit for Create:Source Code

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)

  1. 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.
  2. Update the description of the table to give anybody interacting with it context around the purpose and submit a merge request with the information.
  3. Double check the milestone and introduced_by_url to see if they are accurate

Tables

  • external_status_checks_protected_branches

    • source_code_management is the correct feature category or has been updated
    • external_status_checks_protected_branches description has been updated
    • external_status_checks_protected_branches milestone and introduced_by_url seem accurate
  • fork_network_members

    • source_code_management is the correct feature category or has been updated
    • fork_network_members description has been updated
    • fork_network_members milestone and introduced_by_url seem accurate
  • project_repository_storage_moves

    • source_code_management is the correct feature category or has been updated
    • project_repository_storage_moves description has been updated
    • project_repository_storage_moves milestone and introduced_by_url seem accurate
  • protected_branches

    • source_code_management is the correct feature category or has been updated
    • protected_branches description has been updated
    • protected_branches milestone and introduced_by_url seem accurate
  • approval_project_rules_users

    • source_code_management is the correct feature category or has been updated
    • approval_project_rules_users description has been updated
    • approval_project_rules_users milestone and introduced_by_url seem accurate
  • external_status_checks

    • source_code_management is the correct feature category or has been updated
    • external_status_checks description has been updated
    • external_status_checks milestone and introduced_by_url seem accurate
  • application_settings

    • source_code_management is the correct feature category or has been updated
    • application_settings description has been updated
    • application_settings milestone and introduced_by_url seem accurate
  • trending_projects

    • source_code_management is the correct feature category or has been updated
    • trending_projects description has been updated
    • trending_projects milestone and introduced_by_url seem accurate
  • project_daily_statistics

    • source_code_management is the correct feature category or has been updated
    • project_daily_statistics description has been updated
    • project_daily_statistics milestone and introduced_by_url seem accurate
  • diff_note_positions

    • source_code_management is the correct feature category or has been updated
    • diff_note_positions description has been updated
    • diff_note_positions milestone and introduced_by_url seem accurate
  • namespace_aggregation_schedules

    • source_code_management is the correct feature category or has been updated
    • namespace_aggregation_schedules description has been updated
    • namespace_aggregation_schedules milestone and introduced_by_url seem accurate
  • required_code_owners_sections

    • source_code_management is the correct feature category or has been updated
    • required_code_owners_sections description has been updated
    • required_code_owners_sections milestone and introduced_by_url seem accurate
  • project_repositories

    • source_code_management is the correct feature category or has been updated
    • project_repositories description has been updated
    • project_repositories milestone and introduced_by_url seem accurate
  • project_statistics

    • source_code_management is the correct feature category or has been updated
    • project_statistics description has been updated
    • project_statistics milestone and introduced_by_url seem accurate
  • approval_project_rules

    • source_code_management is the correct feature category or has been updated
    • approval_project_rules description has been updated
    • approval_project_rules milestone and introduced_by_url seem accurate
  • content_blocked_states

    • source_code_management is the correct feature category or has been updated
    • content_blocked_states description has been updated
    • content_blocked_states milestone and introduced_by_url seem accurate
  • approval_project_rules_protected_branches

    • source_code_management is the correct feature category or has been updated
    • approval_project_rules_protected_branches description has been updated
    • approval_project_rules_protected_branches milestone and introduced_by_url seem accurate
  • gpg_key_subkeys

    • source_code_management is the correct feature category or has been updated
    • gpg_key_subkeys description has been updated
    • gpg_key_subkeys milestone and introduced_by_url seem accurate
  • group_merge_request_approval_settings

    • source_code_management is the correct feature category or has been updated
    • group_merge_request_approval_settings description has been updated
    • group_merge_request_approval_settings milestone and introduced_by_url seem accurate
  • project_aliases

    • source_code_management is the correct feature category or has been updated
    • project_aliases description has been updated
    • project_aliases milestone and introduced_by_url seem accurate
  • approval_project_rules_groups

    • source_code_management is the correct feature category or has been updated
    • approval_project_rules_groups description has been updated
    • approval_project_rules_groups milestone and introduced_by_url seem accurate
  • x509_issuers

    • source_code_management is the correct feature category or has been updated
    • x509_issuers description has been updated
    • x509_issuers milestone and introduced_by_url seem accurate
  • merge_request_context_commit_diff_files

    • source_code_management is the correct feature category or has been updated
    • merge_request_context_commit_diff_files description has been updated
    • merge_request_context_commit_diff_files milestone and introduced_by_url seem accurate
  • approval_merge_request_rules_users

    • source_code_management is the correct feature category or has been updated
    • approval_merge_request_rules_users description has been updated
    • approval_merge_request_rules_users milestone and introduced_by_url seem accurate
  • gpg_keys

    • source_code_management is the correct feature category or has been updated
    • gpg_keys description has been updated
    • gpg_keys milestone and introduced_by_url seem accurate
  • remote_mirrors

    • source_code_management is the correct feature category or has been updated
    • remote_mirrors description has been updated
    • remote_mirrors milestone and introduced_by_url seem accurate
  • approval_merge_request_rules_groups

    • source_code_management is the correct feature category or has been updated
    • approval_merge_request_rules_groups description has been updated
    • approval_merge_request_rules_groups milestone and introduced_by_url seem accurate
  • project_repository_states

    • source_code_management is the correct feature category or has been updated
    • project_repository_states description has been updated
    • project_repository_states milestone and introduced_by_url seem accurate
  • approval_merge_request_rule_sources

    • source_code_management is the correct feature category or has been updated
    • approval_merge_request_rule_sources description has been updated
    • approval_merge_request_rule_sources milestone and introduced_by_url seem accurate
  • x509_certificates

    • source_code_management is the correct feature category or has been updated
    • x509_certificates description has been updated
    • x509_certificates milestone and introduced_by_url seem accurate
  • protected_tags

    • source_code_management is the correct feature category or has been updated
    • protected_tags description has been updated
    • protected_tags milestone and introduced_by_url seem accurate
  • approvals

    • source_code_management is the correct feature category or has been updated
    • approvals description has been updated
    • approvals milestone and introduced_by_url seem accurate
  • protected_branch_push_access_levels

    • source_code_management is the correct feature category or has been updated
    • protected_branch_push_access_levels description has been updated
    • protected_branch_push_access_levels milestone and introduced_by_url seem accurate
  • lfs_objects_projects

    • source_code_management is the correct feature category or has been updated
    • lfs_objects_projects description has been updated
    • lfs_objects_projects milestone and introduced_by_url seem accurate
  • external_approval_rules_protected_branches

    • source_code_management is the correct feature category or has been updated
    • external_approval_rules_protected_branches description has been updated
    • external_approval_rules_protected_branches milestone and introduced_by_url seem accurate
  • merge_request_blocks

    • source_code_management is the correct feature category or has been updated
    • merge_request_blocks description has been updated
    • merge_request_blocks milestone and introduced_by_url seem accurate
  • x509_commit_signatures

    • source_code_management is the correct feature category or has been updated
    • x509_commit_signatures description has been updated
    • x509_commit_signatures milestone and introduced_by_url seem accurate
  • protected_branch_merge_access_levels

    • source_code_management is the correct feature category or has been updated
    • protected_branch_merge_access_levels description has been updated
    • protected_branch_merge_access_levels milestone and introduced_by_url seem accurate
  • protected_branch_unprotect_access_levels

    • source_code_management is the correct feature category or has been updated
    • protected_branch_unprotect_access_levels description has been updated
    • protected_branch_unprotect_access_levels milestone and introduced_by_url seem accurate
  • push_event_payloads

    • source_code_management is the correct feature category or has been updated
    • push_event_payloads description has been updated
    • push_event_payloads milestone and introduced_by_url seem accurate
  • draft_notes

    • source_code_management is the correct feature category or has been updated
    • draft_notes description has been updated
    • draft_notes milestone and introduced_by_url seem accurate
  • external_approval_rules

    • source_code_management is the correct feature category or has been updated
    • external_approval_rules description has been updated
    • external_approval_rules milestone and introduced_by_url seem accurate
  • protected_tag_create_access_levels

    • source_code_management is the correct feature category or has been updated
    • protected_tag_create_access_levels description has been updated
    • protected_tag_create_access_levels milestone and introduced_by_url seem accurate
  • approval_merge_request_rules

    • source_code_management is the correct feature category or has been updated
    • approval_merge_request_rules description has been updated
    • approval_merge_request_rules milestone and introduced_by_url seem accurate
  • approver_groups

    • source_code_management is the correct feature category or has been updated
    • approver_groups description has been updated
    • approver_groups milestone and introduced_by_url seem accurate
  • gpg_signatures

    • source_code_management is the correct feature category or has been updated
    • gpg_signatures description has been updated
    • gpg_signatures milestone and introduced_by_url seem accurate
  • repository_languages

    • source_code_management is the correct feature category or has been updated
    • repository_languages description has been updated
    • repository_languages milestone and introduced_by_url seem accurate
  • path_locks

    • source_code_management is the correct feature category or has been updated
    • path_locks description has been updated
    • path_locks milestone and introduced_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.

Edited by Vasilii Iakliushin