Migrating Ops Guides to New Repo

[Aditya23soni]

Overview

We need to move all existing guides to the new repository for guides and templates (knowledgebase-content)

Prerequisite

You need to have

• Manager access to the following drives
  • CoP Google Drives
  • KB-content drive
• Admin access for the repos the issues are in

Action Items

Use the Guide below to migrate all guides related to UI/UX from CoPs to knowledgebase-content. (e.g., there might be a research guide that is relevant to product in the UI/UX community of practice).

• Do steps 1-5
• Add a comment below with the heading and add a link to each of the issues you moved for that CoP

### Guides that are ready to move for lead review
- #

• Move this issue to the Questions/Review column on project board and add the label ready for pm lead
  • Message the lead in the Guides Slack channel by sending a link to the comment with the issues
• lead will sign-off if the issues are ready to move
• once you get sign-off, you can move the issue (step 6 in the guide)
• Check wikis/other resources for references to guides by numbers or names, so no links end up broken
• When you are done, go to Clean Up Guide Issues for Triage #174 and check off the dependency. If all other dependencies are checked off already, then move that issue into the new issue approval column and add it to the team agenda Guides: Meeting Agenda & Minutes #136

Resources/Instructions

• Epic for all CoP guides moves: CoP Templates and Guides Board Migration #169
• Repo: knowledgebase content repo
• Repo Ops CoP Repo
  • Repo, Issue Tab: Search for guides that have not been moved to the Knowlegebase repo
    • Repo, Issue Tab, "Create a Guide" only issue Search for guides that have not been moved to the Knowlegebase repo
• Google Drive: Knowledgebase-content
• Project Board: Guides: Knowledgebase Content Tracker
• Form: Guides Migration Google Form
• Spreadsheet: New Guide Tracker (WIP)
• Guide: How to Move a Guide to a New Repo

[Aditya23soni]

Guides that are ready to move for lead review

• CONTRIBUTING.md ToC out of date ops#146

[ExperimentsInHonesty]

1. Progress: completed prepping 14 issues for guide creation (which is all the guides on this repo)
2. Blockers: Waiting for approval from France to move
3. Availability: Available 7 hours
4. ETA: will be able to move all the issues once blockers transferred.
5. Pictures (if necessary): N/A

[ExperimentsInHonesty]

@Aditya23soni You notified someone who was the author of the issue. The instructions were to notify people who were assigned to the issue. Please do not notify anyone else.

I had unassigned everyone in 2021

@ExperimentsInHonesty ExperimentsInHonesty unassigned NivenPrasad and khushbooshah-PM on Nov 29, 2021

Your comment where you notified him

• Create a Guide/Template: Story Points for your project knowledgebase-content#71

[ExperimentsInHonesty]

Issues that @Aditya23soni did steps 1-5 on

check them off when approved to continue steps 6 onward

• CONTRIBUTING.md ToC out of date ops#146 This issue turned out not to be a guide. I removed the label and reverted it
• Identify and Create Issues for future DevOps Guides ops#132 This issue is an issue to create guides issues. This can stay on their repo.
• Create a deployment checklist for deploying a project into production infrastructure ops#145 This is am issue to create checklists which would eventually go in guides, but right now, are just being hashed out.
• Create a Guide/Template: How to Create Secrets in GitHub knowledgebase-content#67
• Establish RDS end-user database provisioning documentation ops#75 specific to the incubator
• Document our "break-glass" account details ops#71
• Create Docker documentation for Incubator knowledgebase-content#77
• Document setting up individual projects CI/CD pipeline to AWS Incubator using GitHub actions and Docker ops#32
• Create a Guide/Template: Using Docker knowledgebase-content#68
• Create a Guide/Template: Preventing Secrets & Credentials Leaks in GitHub knowledgebase-content#69
• Create a Guide/Template: Hosting for your project knowledgebase-content#70
• Create a Guide/Template: Story Points for your project knowledgebase-content#71
• Create a Guide/Template: How to Troubleshoot 1Password's One-time Password and Use Backup Codes knowledgebase-content#72
• Create a Guide/Template: Setting up one-time passwords in 1Password for use with 2FA in GitHub accounts knowledgebase-content#82

[ExperimentsInHonesty]

The Milestones linked in the agenda are for the CoPs (#131 (comment)), and the KB will need all of 1-6s but the CoPs will need 1-5, and 6-x and all the 6s will be replaced with just Guides.

[ExperimentsInHonesty]

Issues below need to be combined

• Create a Guide/Template: Story Points for your project knowledgebase-content#71
• Create a Guide/Template: Size Labels knowledgebase-content#1

[fchan218]

Closed Issues that need to be checked prior to migration to knowledgebase content repo:

Check off issues that need to be moved

• SPIKE - Explore what logs are available on AWS + Incubator ops#92 does not need to be moved
• Create a Guide for adding Users to AWS  ops#70 does not need to be moved
• Create Guide for setting up project.hcl for deploying on Incubator ops#31 does not need to be moved

[ExperimentsInHonesty]

@Aditya23soni we ended up moving this issue to kb-content after all. All I have done is the transfer, you did copying labels etc steps before...

• can you take look now and see what is left to do Create Docker documentation for Incubator knowledgebase-content#77

[Aditya23soni]

Date: 10/18/2024

1. Progress: Transfered all 7 Issues to Knowledge-based Content.
2. Blockers: None.
3. Availability: 6 hours.
4. ETA: None
5. Pictures (if necessary): N/A

[ExperimentsInHonesty]

The ops repo review and moving of guides to knowlegebase-content has been completed.

• All the guides that should be moved have been.
• All other documentation issues that are not guides for people outside the DevOps team have been changed to just have the wiki label and the word guide replaced with documentation.
• link the knowlegebase-content project board to the repo