You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user, I want tp specifythe location of the state file for a scenario in the molecule.yml
Use cases:
Sharing state between scenarios would allow any one scenario to create, prepare, or destroy infrastructure necessary for testings
Would allow for the grouping of scenarios to share infrastructure for testing
Would eliminate the need for monolithic scenarios in place to simply to minimize the infrastructure provisioning.
Note:
Care will need to be taking by the user if running scenarios in parrellel that share state as a race condition might occur during provsioning. The documented approach might suggest soemthing like running molecule prepare prior to running parrellel scenarios, effectively using the default scenario as the provisioner
Care will need to be taken by the user to disable the destroy step for scenarios using a shared state. If not, this could result in reprovisioning for each scenario. The docuemented approach might be to disable destroy for all but the default scenario
Related #4000 could provide the vars necessary to define the location of the shared state
The text was updated successfully, but these errors were encountered:
As a user, I want tp specifythe location of the state file for a scenario in the molecule.yml
Use cases:
Note:
molecule prepare
prior to running parrellel scenarios, effectively using the default scenario as the provisionerRelated #4000 could provide the vars necessary to define the location of the shared state
The text was updated successfully, but these errors were encountered: