IC Deploying code instead of validating.

[Manjit Singh]

On selecting a component and clicking Force Validate, the command generated by IC is:

C:/Program Files/sfdx/bin/sf.cmd project deploy start -o user-name -c -x C:/Users/xxx/AppData/Local/Temp/package.xml -c --async --json

This results in deployment taking place in the org while IC shows validation is happening (See screenshot of IC #2)

I am guessing it is because of the two -c flags instead, one should have been --dry-run

Sandbox screenshot:

‌

Validation message: Shows as validation but instead it is deploying.

‌

IC Details:

IntelliJ IDEA 2024.1 (Ultimate Edition)
Build #IU-241.14494.240, built on March 28, 2024
Licensed to XXXX
Subscription is active until XXXXX
Runtime version: 17.0.10+8-b1207.12 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 3000M
Cores: 16
Registry:
ide.experimental.ui=true
Non-Bundled Plugins:
com.intellij.mermaid (0.0.22+IJ.232)
com.atlassian.bitbucket.references (2023.1.282)
com.ppolivka.plugin.gitcleaner (1.1.4)
com.majera.intellij.codereview.bitbucket (2024.2.0.241)
com.illuminatedcloud2.intellij (2.3.1.3)
Kotlin: 241.14494.240-IJ

‌

‌

Sfdx Details

@salesforce/cli/1.86.7-legacy.0 win32-x64 node-v18.15.0

[Scott Wells]

Yes, you're correct. The second -c argument is an oversight in the translation from the sfdx command to the sf command. I'll issue a hotfix shortly since this can result in unexpected/unintended changes to the target organization. Thank you for bringing this to my attention.

[Scott Wells]

Delivered in 2.3.1.4.

[Manjit Singh]

Thank you Scott. I have verified this is fixed.

[Scott Wells]

Thank you! I’m just glad that you were able to identify the regression so early after the changes that caused it. Sincere apologies for any inconvenience that it caused while the problem was present.