Upgrade all SFDX Commands to SF Commands

Question

Upgrade all SFDX Commands to SF Commands

GeekStewie opened this issue a year ago · comments

Stewart Anderson commented a year ago

Feature Type

I'm interested in functionality that solves a current problem or limitation in how CumulusCI works.

Does your feature request solve a current problem?

I noticed this in the SFDX update today:

IMPORTANT ANNOUNCEMENT, PLEASE READ: We no longer update sfdx (v7); the last stable version is 7.209.6. You can keep using sfdx (v7) if you want, but it won't contain new features or bug fixes. And we no longer update this page.

And looking at the installers, it now defaults to the SF CLI when you install via npm etc.

I know we have had warnings for a while now but looks like the move needs to happen to ensure we are not using unsupported CLIs

Describe the solution you'd like

Migrate all SFDX commands within CumulusCI to SF equivalents

Describe alternatives you've considered

No response

Additional context

No response

James Estevez · Answer 1 · Tue Jul 18 2023 00:03:38 GMT+0800 (China Standard Time)

Initial work tracked in W-13772594.

Matthew Martin · Answer 2 · Fri Oct 13 2023 03:18:04 GMT+0800 (China Standard Time)

Would really appreciate an update on this, our CTO is considering moving away from CumulusCI depending on if/how soon CCI will transition from SFDX to SF.

Jason Lantz · Answer 3 · Fri Oct 20 2023 01:28:13 GMT+0800 (China Standard Time)

I'm no longer part of the team, but I do want to clarify the message from @GeekStewie's original post. The deprecation message is that they are no longer maintaining the sfdx package itself. The new sf cli package continues to ship with sfdx though. They just don't want you to install the old sfdx package directly anymore. CumulusCI still works fine against the new sf cli installers since they include sfdx.

The warnings call out a few places where CumulusCI's code needs to be updated to use the new commands and environment variables. I'd love to see them gone to avoid this confusion, but I'm reassured knowing that Salesforce is actively using CumulusCI. The Architecture Decision Record (ADR) discussion for this is available at in PR #3630

CumulusCI is actively built against test projects via GitHub Actions including full packaged builds against a test project. Any failures would be pretty quickly detected by those builds.

David Glick · Answer 4 · Fri Oct 20 2023 01:40:11 GMT+0800 (China Standard Time)

@jlantz It looks like the Github Actions need to be updated to install sf rather than sfdx, though: https://github.com/SFDO-Tooling/CumulusCI/blob/main/.github/workflows/feature_test.yml#L77

Jason Lantz · Answer 5 · Fri Oct 20 2023 01:55:16 GMT+0800 (China Standard Time)

@davisagli Great point. That's an easy PR that I'll put together shortly as an early warning system at least.

James Estevez · Answer 6 · Fri Oct 20 2023 04:42:27 GMT+0800 (China Standard Time)

@mattmartin26 Thanks for flagging this. Here's a quick update on the SFDX to SF CLI transition:

We've started work to migrate SFDX commands in CumulusCI to SF. It's on our radar. For details, check out the discussion on the proposed ADR in #3630 (feedback welcome).
As @jlantz mentioned, the new sf CLI still ships with sfdx, commands will still function as expected despite the warnings.
We're adjusting our GitHub Actions per @davisagli's spot, to reflect the ongoing changes.

georgeslater · Answer 7 · Fri Jun 28 2024 01:28:50 GMT+0800 (China Standard Time)

The latest CLI release candidate's release notes states that the force:org:create command will stop working on November 6th, 2024. Is that something to be concerned about?