Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Urgently migrate sfdx source:convert and mdapi:deploy used in local compile to latest sf cli format #687

Open
kgo20240829engie opened this issue Sep 17, 2024 · 4 comments

Comments

@kgo20240829engie
Copy link

Salesforce itself, so your colleagues will remove some commands used by vlocity Build Tool in the localCompile process. see forcedotcom/cli#2974

There is already an alpha work done by vlocity R&D team to migrate to using pure SF commands but not reaching beta or release yet.

Please release things early enough to not have pipelines using localCompile to simply crash because of this communication and alignment mismatch between teams.

@calvinle1
Copy link

calvinle1 commented Oct 19, 2024

Hi Team, is there an update to this? Was initially notified that this is being worked on -- but have not received updates since. Our client has also raised a SF case regarding this

@AbhinavKumar-sf

@AbhinavKumar-sf
Copy link
Collaborator

@kgo20240829engie @calvinle1 @thvd in which code flow you see the usage of this command, we are including alm as node dependency itself

@kgo20240829engie
Copy link
Author

Hi @AbhinavKumar-sf , I don't understand your answer
Firstly, alm is deprecated and now completely unmaintained
Secondly, you offer the possibility to use our own CLI (see your own readme https://github.com/vlocityinc/vlocity_build?tab=readme-ov-file#how-to-use-your-own-sfdx-cli-to-deploy-omniscripts--flexcards-compiled-locally)

Whatever the reason, you should make sure to analyse potential problems and not let old deprecated packages rot, especially since they are colleagues building and maintaining them.

@kgo20240829engie
Copy link
Author

I could add that you already refuse to improve puppeteer order of LWC activation (see #521).
Then the only option clients can use is local compile which is either using a deprecated package that might fail without warning or an up to date CLI that refuses to work because you didn't update the commands used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants