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

sf project deploy report missing objects for non-cached deploy #2603

Closed
quinnpatrick opened this issue Dec 12, 2023 · 3 comments
Closed

sf project deploy report missing objects for non-cached deploy #2603

quinnpatrick opened this issue Dec 12, 2023 · 3 comments
Labels
bug Issue or pull request that identifies or fixes a bug investigating We're actively investigating this issue validated Version information for this issue has been validated

Comments

@quinnpatrick
Copy link

Summary

When a user creates a deployment that includes a CustomField and a different user runs a deploy report (using the job-id & target-org options #2300), there are objects missing from the report. There may be other objects that are not included, but I have noticed this mainly with CustomFields.

Steps To Reproduce

User A creates a deployment with a custom field included.

  • sf project deploy validate -o ORG -x pkgfile -l RunLocalTests

User B runs the deployment report with the deployment ID from User A.

  • sf project deploy report -i deployid-o ORG

Expected result

The Validated Source section of the report should look the same no matter who created the deployment (i.e. all objects included).

Actual result

When User A (the originator of the deploy) runs the "sf project deploy report" the custom field is included.
image
When User B (NOT the originator of the deploy) runs the "sf project deploy report" the custom field is not included.
image
When User B (NOT the originator of the deploy) runs the "sf project deploy report" with "--json" the custom field is included.
image

System Information

Which shell or terminal are you using? bash - via Code Builder

{
  "architecture": "linux-x64",
  "cliVersion": "@salesforce/cli/2.20.6",
  "nodeVersion": "node-v20.9.0",
  "osVersion": "Linux 4.14.255-322-265.538.amzn2.x86_64",
  "rootPath": "/home/codebuilder/.local/share/sf/client/2.20.6-336b6b0",
  "shell": "bash",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.0.2 (core)",
    "@oclif/plugin-commands 3.0.7 (core)",
    "@oclif/plugin-help 6.0.7 (core)",
    "@oclif/plugin-not-found 3.0.4 (core)",
    "@oclif/plugin-plugins 4.1.8 (core)",
    "@oclif/plugin-search 1.0.8 (core)",
    "@oclif/plugin-update 4.1.4 (core)",
    "@oclif/plugin-version 2.0.8 (core)",
    "@oclif/plugin-warn-if-update-available 3.0.4 (core)",
    "@oclif/plugin-which 3.0.11 (core)",
    "@salesforce/cli 2.20.6 (core)",
    "apex 3.0.8 (core)",
    "auth 3.0.8 (core)",
    "data 3.0.2 (core)",
    "deploy-retrieve 2.2.0 (core)",
    "info 3.0.5 (core)",
    "limits 3.0.4 (core)",
    "marketplace 1.0.7 (core)",
    "org 3.0.9 (core)",
    "packaging 1.27.3 (core)",
    "schema 3.0.6 (core)",
    "settings 2.0.9 (core)",
    "sobject 1.0.2 (core)",
    "source 3.0.1 (core)",
    "telemetry 3.1.3 (core)",
    "templates 56.0.3 (core)",
    "trust 3.0.6 (core)",
    "user 3.0.6 (core)",
    "sfdx-plugin-prettier 1.0.5 (user)",
    "sfdx-plugin-source-read 1.2.0 (user)"
  ]
}
@quinnpatrick quinnpatrick added the investigating We're actively investigating this issue label Dec 12, 2023
Copy link

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 github-actions bot added the validated Version information for this issue has been validated label Dec 12, 2023
@iowillhoit
Copy link
Contributor

Hey @quinnpatrick, It looks like this is happening because the CustomField is being Created and does not exist on User B's machine. I would guess that we are resolving the Path for results coming back from the server and omitting them if they are not found locally. We could handle this better, I'll get a ticket created. Thanks for submitting this!

@iowillhoit iowillhoit added the bug Issue or pull request that identifies or fixes a bug label Dec 15, 2023
Copy link

git2gus bot commented Dec 15, 2023

This issue has been linked to a new work item: W-14675377

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue or pull request that identifies or fixes a bug investigating We're actively investigating this issue validated Version information for this issue has been validated
Projects
None yet
Development

No branches or pull requests

3 participants