sf-deploy-metadata not able to recognize change metadata for deployment
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- cli
Research direction
Reproduce the issue with the sf-deploy-metadata tool using the supplied directory and usernameOrAlias, then compare it with sf project deploy start. Inspect the tool's change-detection or deployment entry point; done means the tool recognizes the five new CustomField metadata files and deploys them instead of reporting no local changes.
Written by the indexing model from the issue text.
Description
Having agent to create some fields and then letting him to call sf-deploy-metadata resolves in message No local changes to deploy were found.. But running sf project deploy start manually correctly deploys new metadata.
Agent
Use Tool: sf-deploy-metadata (sf-deploy-metadata-8)
{ "usernameOrAlias": "carvago-dev", "directory": "/Users/adam/IdeaProjects/salesforce" }Tool Results: sf-deploy-metadata-8
No local changes to deploy were found.
Manual deployment
adam@Mac:~/IdeaProjects/salesforce|WI-002370⚡ ⇒ sf project deploy start
─────────────── Deploying Metadata ───────────────
Deploying v64.0 metadata to [email protected] using the v64.0 SOAP API.
✔ Preparing 110ms
✔ Waiting for the org to respond 654ms
✔ Deploying Metadata 2.17s
▸ Components: 5/5 (100%)
◯ Running Tests - Skipped
✔ Updating Source Tracking 2.05s
▸ Members: 5/5 (100%)
✔ Done 0ms
Status: Succeeded
Deploy ID: 0AfAU00000UAikt0AD
Target Org: [email protected]
Elapsed Time: 4.97s
Deployed Source
┌─────────┬───────────────────────────────────────────┬─────────────┬─────────────────────────────┐
│ State │ Name │ Type │ Path │
├─────────┼───────────────────────────────────────────┼─────────────┼─────────────────────────────┤
│ Created │ Case.PCC_Information_Received_Date__c │ CustomField │ force-app/main/default/obje │
│ │ │ │ cts/Case/fields/PCC_Informa │
│ │ │ │ tion_Received_Date__c.field │
│ │ │ │ -meta.xml │
│ Created │ Case.PCC_New_PCC_Date__c │ CustomField │ force-app/main/default/obje │
│ │ │ │ cts/Case/fields/PCC_New_PCC │
│ │ │ │ _Date__c.field-meta.xml │
│ Created │ Case.PCC_Partner_Car_Check_Closed_Date__c │ CustomField │ force-app/main/default/obje │
│ │ │ │ cts/Case/fields/PCC_Partner │
│ │ │ │ _Car_Check_Closed_Date__c.f │
│ │ │ │ ield-meta.xml │
│ Created │ Case.PCC_Partner_Car_Check_Done_Date__c │ CustomField │ force-app/main/default/obje │
│ │ │ │ cts/Case/fields/PCC_Partner │
│ │ │ │ _Car_Check_Done_Date__c.fie │
│ │ │ │ ld-meta.xml │
│ Created │ Case.PCC_Request_Sent_Date__c │ CustomField │ force-app/main/default/obje │
│ │ │ │ cts/Case/fields/PCC_Request │
│ │ │ │ _Sent_Date__c.field-meta.xm │
│ │ │ │ l │
└─────────┴───────────────────────────────────────────┴─────────────┴─────────────────────────────┘
- Dominant language
- No language data
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
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 1/5 1-3 hours Newbie friendliness 84/100
NousResearch/hermes-agent#129038 ·
Maintainers usually reply within 1 day
-
customer-reported
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/azure-cli#34150 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
WeblateOrg/translation-finder#1099 ·
Maintainers usually reply within 1 day
-
area: global bug dx priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day