Let's stub out a basic lando new-project command. For now we dont need to worry about connecting and authenticating with the Tandem Hub, let's just make placeholder functions to simulate interacting with it that return the data we need.
To kick this off lets
Have lando new-project do authentication similar to the pantheon integration eg token based auth that is saved locally. For now lets just authenticate against a list of all our emails.
Product a list of start states. Again, these can be hardcoded for now until Tandem Hub is fully operational @labboy0276 can likely give you the relevant metadata
Ask for a name of the project
Clone the project down and modify/create a lando file with the correct name
[x] I've selected at most two labels that best describe what part of the business this ticket improves eg sales, dev, etc
[x] I've added a story point estimation. This should never exceed 3!!!
[x] I've created a follow up task or discussion and linked to it in the section below or labeled this as a "one-off" task if there is no follow up task
What is to be done?
Using the loose spec over here https://github.com/thinktandem/lando-tandem#new-project
Let's stub out a basic
lando new-project
command. For now we dont need to worry about connecting and authenticating with the Tandem Hub, let's just make placeholder functions to simulate interacting with it that return the data we need.To kick this off lets
lando new-project
do authentication similar to the pantheon integration eg token based auth that is saved locally. For now lets just authenticate against a list of all our emails.Task checklist
sales
,dev
, etcNext steps(s)
The below all need tickets eventually