Does this change brings modularity needed to incorporate both AWS and Azure into a single CLI?
In my head the CLI would converge into another project which depends on both Azure and AWS Library and handle each cloud as subcommands.
Notes from meeting:
Reasons to go with split CLI per service: doesn't scale up when new services are added
Reasons to go for monolithic CLI: easier to maintain from a single team perspective
In the future there can be a generalized library to handle energy labels
Speed of releasing is key according to Theodoor
Decisions, consensus:
Package the split projects as they are (AWS and Azure) into a Docker;
Does this change brings modularity needed to incorporate both AWS and Azure into a single CLI? In my head the CLI would converge into another project which depends on both Azure and AWS Library and handle each cloud as subcommands.
Notes from meeting:
Decisions, consensus: