tool sf-deploy-metadata does not provides details
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by tracing the sf-deploy-metadata tool and its use of sf project deploy start. Check where failed deployment output is reduced to a conflict count, then verify that the tool result exposes enough deployment details for an agent to identify missing metadata.
Written by the indexing model from the issue text.
Description
Hi, when agent runs the sf-deploy-metadata tool, and the deployment fails, it does not provide detailed information about the issue, just how many conflicts occured.
**Tool Results: sf-deploy-metadata-86**
Failed to deploy metadata: 6 conflicts detected
The output of sf project deploy start should be routed to the tool result such that the agent can react. For example, I want the agent to deploy the project, which I know have some issues related to missing metadata, those can be easily resolved by deploying the missing metadata, but for this to work the agent needs to know what metadata is missing.
Whole agent thread:
xx Dev Deployment and MCP Recovery
User
deploy this salesforce project to xx-dev. if deployment fails, deploy indidividual files in order to fix the deployment, use mcp server where possible
Agent
Use Tool: sf-get-username (sf-get-username-85)
{ "directory": "/Users/adam/IdeaProjects/salesforce", "defaultTargetOrg": false }Tool Results: sf-get-username-85
YOU MUST inform the user that we are going to use "[email protected]" (Alias: xx-dev) for the "usernameOrAlias" parameter.
YOU MUST explain the reasoning for selecting this org, which is: "it is the default (Local) target org"
UNLESS THE USER SPECIFIES OTHERWISE, use this username for the "usernameOrAlias" parameter in future Tool calls.Agent
I will deploy your Salesforce project to the
xx-devorg using[email protected].Use Tool: sf-deploy-metadata (sf-deploy-metadata-86)
{ "usernameOrAlias": "xx-dev", "apexTestLevel": "NoTestRun", "directory": "/Users/adam/IdeaProjects/salesforce" }Tool Results: sf-deploy-metadata-86
Failed to deploy metadata: 6 conflicts detected
Agent
The deployment to
xx-devfailed with 6 conflicts. Unfortunately, thesf-deploy-metadatatool doesn't provide specific details about which files caused the conflicts directly in its output.To address this, I will try to find all Salesforce metadata files in your project and then attempt to deploy them individually. I will start by finding all files within the
/Users/adam/IdeaProjects/salesforcedirectory.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from forcedotcom/mcp
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
forcedotcom/mcp#44 ·
-
investigating
Difficulty 4/5 3-5 days Newbie friendliness 35/100
forcedotcom/mcp#43 · 1 comment ·
-
investigating
Difficulty 4/5 3-5 days Newbie friendliness 38/100
forcedotcom/mcp#42 · 1 comment ·
-
investigating
Difficulty 4/5 3-5 days Newbie friendliness 48/100
forcedotcom/mcp#41 · 2 comments ·
-
investigating
Difficulty 3/5 1-2 days Newbie friendliness 35/100
forcedotcom/mcp#35 · 2 comments · 2 reactions ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
[Request]: Snow ShotOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ScoopInstaller/Extras#18870 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
foundation/inky#334 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NVIDIA/nvmesh-utils#9 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day