#note [Feature] Implement `source-wand onboard`

[atandrewlee]

Other Requirements

• [Issue] With Go, how do we deal with version name when it's the commit hash? #23 : Need to figure this out for our sourcecraft-track field

Algorithm

• Read the dependencies.yaml and re-create the dependency tree
• Find all of the nodes that have no dependencies underneath them
• Complete those resolutions (so that they now all have a pointer to Sourcecraft)

Question: How do we repeat this & do this in the correct order?

• (+) Do things in parallel

Question: How automated should this be?

• Do we want it to run all the way through and skip the ones it doesn't complete?
• Or do we want to make it more "interactive" where human input is needed at each step (per level) to onboard everything?

Manual Checks

• Test the sourcecraft.yaml (Does It Work?) >> sourcecraft build

• When pushing to sourcecraft, it takes time for it to build on that side

• Question: If the sourcecraft.yaml doesn't work, should it stop & tell them to fix it?

Algorithm For Each Node

• Clone the repository (already exists or create new)
• Pull from upstream
• Setup the remotes
• (Sourcecraft init) >> Based on Rules
• Push to Launchpad
• ((Testing Stage)) >> Does it build properly???
• Register & Push to Sourcecraft

Protocol

Where do we want to push the code?

• Answer: There's an "FE Everything LTS team" where we can push all the code to
• https://launchpad.net/~fe-everything-lts

Future Enhancements

[atandrewlee]

Note Sheet

source-wand init

• start at /cli/src/commands/init.rs

• calls find_dependency_tree (in /dependency-analysis/src/lib.rs)

• gets project manipulator (Local, Git, etc.) & build system

• gets all the required dependencies -> list

• calls plan_onboarding (in /onboarding/src/plan/plan_onboarding.rs)

• This creates all of the files (the dependencies.yaml file is created first)

---

• There's a function read_yaml_file that can read dependencies.yaml
• Question: What does write_yaml_file and read_yaml_file exactly do?