New Option `load_sfdx_project_paths` for dx_convert_from Task about cumulusci HOT 5 OPEN

I agree - I am just getting started ;-) Jokes aside - I started with this particular feature because I am a beginner in Python.

Happy to support this adventure but also happy if someone more experienced takes over and this PR goes away.

from cumulusci.

I completed the code and tests leveraging existing methods from Project Config and can contribute a PR if a branch is provided.

from cumulusci.

@Szandor72 awesome! In my experience you can submit a PR from your forked repo as a way of contributing. I don't believe you need to point it at a particular branch: https://github.com/SFDO-Tooling/CumulusCI/blob/main/docs/contributing.md#pull-request-guidelines

from cumulusci.

I created a draft PR @Julian88Tex - there are some checks failing.

Before marking it ready for review, I also like to test it with one or two real sfdx projects.

from cumulusci.

@Szandor72 sorry for the delay! I've been out at a few conferences (TDX & SXSW) so I'm still catching up on emails. Thanks so much for creating the PR and pushing forward this idea. I think your change makes sense to me. That being said, I'm also curious about getting a bit more input from the CumulusCI team (CC @davidmreed) because I'm wondering if it makes more sense to solve this in a more holistic way. Beyond just the dx_convert_from command there are a number of situations where I would hope that CumulusCI could deal with multiple paths. Some other examples are deploy & uninstall_packaged_incremental.

from cumulusci.