search

vlocityinc / vlocity_build

Vlocity Build is a command line tool to export and deploy Vlocity DataPacks in a source control friendly format through a YAML Manifest describing your project. Its primary goal is to enable Continuous Integration for Vlocity Metadata through source control. It is written as a Node.js module.
MIT License
113 stars 98 forks source link

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

Open kgo20240829engie opened 1 month ago

kgo20240829engie commented 1 month ago

Salesforce itself, so your colleagues will remove some commands used by vlocity Build Tool in the localCompile process. see https://github.com/forcedotcom/cli/issues/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 commented 1 week ago

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 commented 5 days ago

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

kgo20240829engie commented 5 days ago

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 commented 5 days ago

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.