Skip to content

Commit 69a9075

Browse files
fix: replace hardcoded 'sf' with config.bin for sfdx use
1 parent 7a83740 commit 69a9075

16 files changed

+33
-29
lines changed

messages/delete.source.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Delete source from your project and from a non-source-tracked org.
44

55
# description
66

7-
Use this command to delete components from orgs that don’t have source tracking. To remove deleted items from orgs that have source tracking enabled, "sf project deploy start".
7+
Use this command to delete components from orgs that don’t have source tracking. To remove deleted items from orgs that have source tracking enabled, "<%= config.bin %> project deploy start".
88

99
When you run this command, both the local source file and the metadata component in the org are deleted.
1010

messages/deploy.async.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,12 +8,12 @@ Deploy has been queued for cancellation.
88

99
# info.AsyncDeployCancel
1010

11-
Run "sf project deploy cancel --job-id %s" to cancel the deploy.
11+
Run "%s project deploy cancel --job-id %s" to cancel the deploy.
1212

1313
# info.AsyncDeployStatus
1414

15-
Run "sf project deploy report --job-id %s" to get the latest status.
15+
Run "%s project deploy report --job-id %s" to get the latest status.
1616

1717
# info.AsyncDeployResume
1818

19-
Run "sf project deploy resume --job-id %s" to resume watching the deploy.
19+
Run "%s project deploy resume --job-id %s" to resume watching the deploy.

messages/deploy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ For example, if your local project contains a source directory with metadata fil
1212

1313
The command stores your responses in the "deploy-options.json" file in your local project directory and uses them as defaults when you rerun the command. Specify --interactive to force the command to reprompt.
1414

15-
Use this command for quick and simple deploys. For more complicated deployments, use the environment-specific commands, such as "sf project deploy start", that provide additional flags.
15+
Use this command for quick and simple deploys. For more complicated deployments, use the environment-specific commands, such as "<%= config.bin %> project deploy start", that provide additional flags.
1616

1717
# examples
1818

messages/deploy.metadata.cancel.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,15 +47,15 @@ Number of minutes to wait for the command to complete and display results.
4747

4848
# flags.wait.description
4949

50-
If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To resume watching the cancellation, run "sf project deploy resume". To check the status of the cancellation, run "<%= config.bin %> project deploy report".
50+
If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To resume watching the cancellation, run "<%= config.bin %> project deploy resume". To check the status of the cancellation, run "<%= config.bin %> project deploy report".
5151

5252
# flags.async.summary
5353

5454
Run the command asynchronously.
5555

5656
# flags.async.description
5757

58-
The command immediately returns the control of the terminal to you. This way, you can continue to use the CLI. To resume watching the cancellation, run "sf project deploy resume". To check the status of the cancellation, run "<%= config.bin %> project deploy report".
58+
The command immediately returns the control of the terminal to you. This way, you can continue to use the CLI. To resume watching the cancellation, run "<%= config.bin %> project deploy resume". To check the status of the cancellation, run "<%= config.bin %> project deploy report".
5959

6060
# error.CannotCancelDeploy
6161

messages/deploy.metadata.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ Number of minutes to wait for command to complete and display results.
110110

111111
# flags.wait.description
112112

113-
If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To resume the deployment, run "sf project deploy resume". To check the status of the deployment, run "sf project deploy report".
113+
If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To resume the deployment, run "<%= config.bin %> project deploy resume". To check the status of the deployment, run "<%= config.bin %> project deploy report".
114114

115115
# flags.manifest.summary
116116

@@ -178,7 +178,7 @@ Run the command asynchronously.
178178

179179
# flags.async.description
180180

181-
The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the CLI. To resume the deployment, run "sf project deploy resume". To check the status of the deployment, run "sf project deploy report".
181+
The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the CLI. To resume the deployment, run "<%= config.bin %> project deploy resume". To check the status of the deployment, run "<%= config.bin %> project deploy report".
182182

183183
# flags.metadata-dir.summary
184184

@@ -203,7 +203,7 @@ You must specify tests using the --tests flag if the --test-level flag is set to
203203

204204
# error.ClientTimeout
205205

206-
The command has timed out, although the deployment is still running. Use "sf project deploy resume" to resume watching the deployment.
206+
The command has timed out, although the deployment is still running. Use "%s project deploy resume" to resume watching the deployment.
207207

208208
# error.Conflicts
209209

@@ -213,15 +213,15 @@ There are changes in the org that conflict with the local changes you're trying
213213

214214
- To overwrite the remote changes, rerun this command with the --ignore-conflicts flag.
215215

216-
- To overwrite the local changes, run the "sf project retrieve start" command with the --ignore-conflicts flag.
216+
- To overwrite the local changes, run the "%s project retrieve start" command with the --ignore-conflicts flag.
217217

218218
# error.nothingToDeploy
219219

220220
No local changes to deploy.
221221

222222
# error.nothingToDeploy.Actions
223223

224-
- To see conflicts and ignored files, run "sf project deploy preview" with any of the manifest, directory, or metadata flags.
224+
- To see conflicts and ignored files, run "%s project deploy preview" with any of the manifest, directory, or metadata flags.
225225

226226
# flags.junit
227227

messages/deploy.metadata.preview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,4 +94,4 @@ There are changes in the org that conflict with the local changes you're trying
9494

9595
- To overwrite the remote changes, rerun this command with the --ignore-conflicts flag.
9696

97-
- To overwrite the local changes, run the "sf project retrieve start" command with the --ignore-conflicts flag.
97+
- To overwrite the local changes, run the "%s project retrieve start" command with the --ignore-conflicts flag.

messages/retrieve.metadata.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -157,7 +157,7 @@ There are changes in your local files that conflict with the org changes you're
157157

158158
- To overwrite the local changes, rerun this command with the --ignore-conflicts flag.
159159

160-
- To overwrite the remote changes, run the "sf project deploy start" command with the --ignore-conflicts flag.
160+
- To overwrite the remote changes, run the "%s project deploy start" command with the --ignore-conflicts flag.
161161

162162
# info.WroteZipFile
163163

src/commands/project/deploy/cancel.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ export default class DeployMetadataCancel extends SfCommand<DeployResultJson> {
7777

7878
if (flags.async) {
7979
const asyncResult = await cancelDeployAsync({ 'target-org': deployOpts['target-org'] }, jobId);
80-
const formatter = new AsyncDeployCancelResultFormatter(asyncResult.id);
80+
const formatter = new AsyncDeployCancelResultFormatter(asyncResult.id, this.config.bin);
8181
if (!this.jsonEnabled()) formatter.display();
8282
return formatter.getJson();
8383
} else {

src/commands/project/deploy/quick.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ export default class DeployMetadataQuick extends SfCommand<DeployResultJson> {
9797
this.log(`Deploy ID: ${bold(jobId)}`);
9898

9999
if (flags.async) {
100-
const asyncFormatter = new AsyncDeployResultFormatter(jobId);
100+
const asyncFormatter = new AsyncDeployResultFormatter(jobId, 'sf');
101101
if (!this.jsonEnabled()) asyncFormatter.display();
102102
return asyncFormatter.getJson();
103103
}

src/commands/project/deploy/resume.ts

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -92,6 +92,7 @@ export default class DeployMetadataResume extends SfCommand<DeployResultJson> {
9292
const { deploy, componentSet } = await executeDeploy(
9393
// there will always be conflicts on a resume if anything deployed--the changes on the server are not synced to local
9494
{ ...deployOpts, wait, 'dry-run': false, 'ignore-conflicts': true },
95+
this.config.bin,
9596
this.project,
9697
jobId
9798
);

0 commit comments

Comments
 (0)