Skip to content

Update new data source page

Dennis van Rooijen requested to merge master-patch-50e7 into master

Why is this change being made?

On some of the new data source request that came in in the past, we saw that using (complex) JSON data is not always straightforward. Formalizing with this MR that a Data Engineer can support or can take over flattening the data to a tabular format, from where it can be picked up by other GitLab Team members to model it towards PROD.

Author Checklist

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Edited by Dennis van Rooijen

Merge request reports