As a developer, I want to improvise the usage of various platform operations.
Currently to run, lets say add-organisation operation in fabric, developer has to go inside the fabric platform and execute the playbook individually.
Here I propose 2 solutions, both of which can be implemented together to provide this feature across platforms
Just like site.yaml (master playbook to deploy networks), we can rework on its name, and introduce several other master playbooks like (like the master playbook we currently have for add-org)
platform-deploy.yaml (This playbook can control both setup and resetting of the network)
platform-ops.yaml (This playbook can act as the master playbook to perform available platform operations)
For this, to enable various platform operations, all we can expect the users is to pass variables like operation=add_org (just like how we do it for reset: reset=true)
Enable the above features from the network.yaml itself, by introducing a top-level field such as network.operation=reset or network.operation=add_org
The tags we use for these operations should be uniform across platforms, while introducing unique tags for unique platform-specific features, along with the updation of operation guides, and the operation-tag matrix to list out all available tags with their usage and references to the operation guides for each tag.
This will also help us maintaining the available/deprecated features just by introducing and deprecating the referenced tag for the same
TODO: Create platform specific issues for this epic completion
Description
As a developer, I want to improvise the usage of various platform operations. Currently to run, lets say
add-organisation
operation in fabric, developer has to go inside the fabric platform and execute the playbook individually.Here I propose 2 solutions, both of which can be implemented together to provide this feature across platforms
site.yaml
(master playbook to deploy networks), we can rework on its name, and introduce several other master playbooks like (like the master playbook we currently have for add-org)For this, to enable various platform operations, all we can expect the users is to pass variables like
operation=add_org
(just like how we do it for reset:reset=true
)network.operation=reset
ornetwork.operation=add_org
The tags we use for these operations should be uniform across platforms, while introducing unique tags for unique platform-specific features, along with the updation of operation guides, and the operation-tag matrix to list out all available tags with their usage and references to the operation guides for each tag. This will also help us maintaining the available/deprecated features just by introducing and deprecating the referenced tag for the same
TODO: Create platform specific issues for this epic completion