data team aws guide
Why is this change being made?
💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.Please add the details saying why, not just what in this section. Example:
We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.
Add instructions for aws
for the data platform team
Author and Reviewer Checklist
Please verify the check list and ensure to tick them off before the MR is merged.
-
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 DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
For transparency, share this MR with the audience that will be impacted. -
Team: For changes that affect your direct team, share in your group Slack channel -
Department: If the update affects your department, share the MR in your department Slack channel -
Division: If the update affects your division, share the MR in your division Slack channel -
Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-
Commits
- data team aws guide
Merge request reports
Activity
added HandbookContent label
assigned to @juwong
Using combined codequality.json: markdownlint-cli2-codequality.json vale-codequality.json linkcheck.json
⚠️ Pipeline Failure - Linting ErrorsOne of the linters has reported errors and as a result the pipeline has failed. Once the pipeline completes, you'll find the code quality report above which can link you to where the error is in your code. Additionally, below you'll find a table of the errors. The table has links to the lint rules so you can find more information on how to fix the issue(s).
Rule File Line Error MD041 content/handbook/enterprise-data/platform/aws-guide.md 1 First line in a file should be a top-level heading handbook.FrontmatterTitle content/handbook/enterprise-data/platform/aws-guide.md 1 Page must have title specified in frontmatter. ⚠️ If you are renaming, moving, or deleting pages, please check the Code Quality report, or the hugolint job's artifact files, to see if there are any related broken links.If you need more help please reach out on Slack in #mr-buddies.
- Resolved by ved prakash
@vedprakash2021 - can you please review?
requested review from @vedprakash2021
started a merge train
mentioned in commit 3acd3f4d