CD should be the focus now, i.e. the entry point should be some form of rover cd --config=foo command to carry out landing zones and launchpad operations, these can then be internally "ported" over to launchpad and landingzone commands and the settings which are in symphony YAML.
The internal implementation, namely the terraform actions, interaction with state etc will remain the same regardless.
This task is to get stub functionality for CD working, reading symphony YAML, looping over it or locating a level or stack in the YAML and outputing simple log messages for now
Then we can follow up with deeper implementation
14 is a pre-req
rover cd always requires a symphony.yaml config file as input
Do we need to modify the existing symphony YAML schema? (investigation)
CD should be the focus now, i.e. the entry point should be some form of
rover cd --config=foocommand to carry out landing zones and launchpad operations, these can then be internally "ported" over to launchpad and landingzone commands and the settings which are in symphony YAML.The internal implementation, namely the terraform actions, interaction with state etc will remain the same regardless.
This task is to get stub functionality for CD working, reading symphony YAML, looping over it or locating a level or stack in the YAML and outputing simple log messages for now
Then we can follow up with deeper implementation
14 is a pre-req
rover cdalways requires a symphony.yaml config file as input