I'm interested in extensions to existing CumulusCI functionality (e.g., broader applicability of an existing Task or Flow).
Does your feature request solve a current problem?
Currently we need to maintain two dev.json org config files and ensure they are kept in sync, so that at the core preview window we can load a scratch org onto the preview of the core release. The only difference in the two files is the addition of the line "release": "preview",
To maintain one file removes any human error when keeping the files in sync.
Describe the solution you'd like
When creating an org with a flow like dev_org or qa_org be able to set preview at the end. This could also work for previous, which may be needed in certain scenarios.
Example:
cci flow run dev_org --org dev --preview
This would then take the dev.json file (or whatever file has been set for the dev org config) and create a temp copy with the "release: preview " line added. Then use that to create the org.
Describe alternatives you've considered
Maintaining two files.
Adding a script which could then handle the option however this would then need to be maintained as cci evolves.
Feature Type
I'm interested in extensions to existing CumulusCI functionality (e.g., broader applicability of an existing Task or Flow).
Does your feature request solve a current problem?
Currently we need to maintain two dev.json org config files and ensure they are kept in sync, so that at the core preview window we can load a scratch org onto the preview of the core release. The only difference in the two files is the addition of the line
"release": "preview",
To maintain one file removes any human error when keeping the files in sync.
Describe the solution you'd like
When creating an org with a flow like dev_org or qa_org be able to set preview at the end. This could also work for previous, which may be needed in certain scenarios.
Example: cci flow run dev_org --org dev --preview
This would then take the dev.json file (or whatever file has been set for the dev org config) and create a temp copy with the "release: preview " line added. Then use that to create the org.
Describe alternatives you've considered
Maintaining two files.
Adding a script which could then handle the option however this would then need to be maintained as cci evolves.
Additional context
No response