SFDO-Tooling / CumulusCI

Python framework for building portable automation for Salesforce projects
http://cumulusci.readthedocs.io
BSD 3-Clause "New" or "Revised" License
363 stars 242 forks source link

Flow "push_upgrade_org" is incorrectly defined #3758

Open RupertBarrow opened 9 months ago

RupertBarrow commented 9 months ago

Describe the bug

The push_upgrade_org flow is configured as follows :

Flow Steps
1) flow: dependencies [from current folder]
    1) task: update_dependencies
    2) task: deploy_pre
       options:
           path: unpackaged/pre
2) task: install_managed
   options:
       version: latest
3) task: update_dependencies
   options:
       security_type: NONE
       resolution_strategy: include_beta
4) task: install_managed_beta
   options:
       version: latest_beta
       security_type: NONE
5) flow: config_qa
    1) task: deploy_post
       options:
           path: unpackaged/post
    2) task: update_admin_profile
    90) task: load_sample_data

The flow called in step 5 should be "config_managed" and not "config_qa". They are both defined the same way with the following steps :

1) task: deploy_post
2) task: update_admin_profile
90) task: load_sample_data

but for syntax and customisability, it would be nice to fix this.

Reproduction steps

  1. Read the docs :
  2. https://cumulusci.readthedocs.io/en/stable/flows.html#push-upgrade-org
  3. https://cumulusci.readthedocs.io/en/stable/flows.html#config-qa
  4. https://cumulusci.readthedocs.io/en/stable/flows.html#config-managed

Push upgrades do not take place during QA but rather during installation of the managed packaged, eg in a UAT sandbox.

Your CumulusCI and Python versions

CumulusCI version: 3.84.2 (/Users/rupert/.local/bin/cci) Python version: 3.11.5 (/Users/rupert/.local/pipx/venvs/cumulusci/bin/python)

Operating System

MacOS 12.7.3

Windows environment

No response

CumulusCI installation method

pipx

Error Gist

No response

Additional information

No response