Open ArielS1 opened 4 years ago
Hello,
Very good point. I think in the future, the best would be to use source format. This package generation tool could be refactored using a sfdx plugin. This way it will be able to benefit from the sfdx project connection and retrieve the metadata version of the target sandbox (and so deal with preview easily).
Another way is to use the vs code extension. I don't know how it is done
But still not everybody use this package with a UI or with VS code and it should also support cli auth using a username and password, this is what i specificly need anyway. and if needed the auth method can be extended to support sfdx, certificate or whatever
Hi,
I would like to consult with you about a change i want to make. The idea is to run the metadata API each time to retrieve the version specific metadata so it will be future proof without having to update metadata.js manually in the repository each version release.
The user will have to input in the cli a username and password of an org (any org, since the metadata api result will be the same for every org) and build the metadata.js in memory instead of using metadata.js repository file.
The problem is that i guess not every company will be willing to make a callout from this package, or to input their org credentials.
So there are few options:
Please tell me what is your preferred work of action and i'll try to implement. If you would like to discuss further about it, you can get my email from Ben Bozou.
Best regards,
Ariel