Warnings of Resources Not Found in Local Project During Deployment Report #2862
Comments
|
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
github-actions
bot
added
the
validated
|
@Alfystar Take a look at the 2.38.7 release notes. Those warnings were added to solve an issue with |
|
Thank you, I understand now, but I think this output is not correct, all the deployed resources were present on the project on which the report was run, more over, the deleted resources are correctly missing in project |
|
I don't think it's the correct result because the report is called on the same machine that performed the deployment, just 1 cmd before Furthermore, the logs generated with version 2.38.7, which as you rightly pointed out solved the problem, did not show these warnings, in the same configuration and on the same machine Same situation for logs generated with 2.39.6 The first time they appeared was today with version 2.40.7 The code automatically updates to the latest stable version of sf-cli |
|
@Alfystar Are you able to provide a repository that replicates the issue you're seeing? The steps you provided don't replicate the issue using dreamhouse-lwc |
|
I try to recreate the problem and then share the repository with you. However, I realized that I didn't specify that our workflow is to generate a package in metadata format, from the source of the repository using sf-cli and then deploy that package, it's an important detail I think. We inherited this flow from the structure we had with ANT, and too much was developed on that basis to abandon it completely, moreover reading the documentation I seemed to understand that internally sf-cli still creates a package in metadata format |
|
I recreated a scratch org as described in your readme in the repository: I used the tools we developed to exactly recreate the problem with a deploy/delete validator of the apex classes. I used our company tools to create the packages, but as you can easily see, the program logs clearly show which sf-cli commands are executed. The part with the unexpected warnings is at the end of the log. I hope that this evidence is sufficient and allows you to understand and solve this little problem introduced in this release. |
|
Ah I didn't realize that you were running |
mdonnalley
added
bug
|
This issue has been linked to a new work item: W-15735078 |
Don't worry, I didn't actually say it for granted, my mistake |
|
This issue is fixed in the 2.42.6 (May 22, 2024) release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
After updating to version 2.40.7 of the Salesforce CLI, we started receiving warnings in our pipeline log. These warnings indicate that there are custom fields and Apex classes present in the Salesforce org but not found in the local project, despite the deployment operation completing successfully.
Steps to Reproduce
sf project deploy report --target-org <orgName> --job-id <jobID> --json.Expected Result
There should be no warnings about resources not found in the local project if they have been correctly handled in the package.xml and in the repository.
Actual Result
We receive warnings for resources not found in the local project, even though the deployment operations have been executed successfully and the resources are present in the package.xml and in the repository.
System Information
{ "architecture": "darwin-arm64", "cliVersion": "@salesforce/cli/2.40.7", "nodeVersion": "node-v20.12.2", "osVersion": "Darwin 23.4.0", "rootPath": "/Users/ea_enel/.local/share/sf/client/2.40.7-bde121f", "shell": "zsh", "pluginVersions": [ "@oclif/plugin-autocomplete 3.0.16 (core)", "@oclif/plugin-commands 3.3.1 (core)", "@oclif/plugin-help 6.0.21 (core)", "@oclif/plugin-not-found 3.1.7 (core)", "@oclif/plugin-plugins 5.0.18 (core)", "@oclif/plugin-search 1.0.23 (core)", "@oclif/plugin-update 4.2.9 (core)", "@oclif/plugin-version 2.0.17 (core)", "@oclif/plugin-warn-if-update-available 3.0.16 (core)", "@oclif/plugin-which 3.1.8 (core)", "@salesforce/cli 2.40.7 (core)", "apex 3.1.11 (core)", "auth 3.6.5 (core)", "data 3.3.2 (core)", "deploy-retrieve 3.6.8 (core)", "info 3.2.4 (core)", "limits 3.3.4 (core)", "marketplace 1.2.4 (core)", "org 4.1.5 (core)", "packaging 2.4.1 (core)", "schema 3.3.4 (core)", "settings 2.2.3 (core)", "sobject 1.3.6 (core)", "source 3.3.5 (core)", "telemetry 3.3.4 (core)", "templates 56.2.4 (core)", "trust 3.6.7 (core)", "user 3.5.4 (core)", "sfdx-plugin-source-read 1.2.0 (user)" ] }The text was updated successfully, but these errors were encountered: