You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: messages/clone.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,6 @@
2
2
3
3
Clone a sandbox org.
4
4
5
-
# success
6
-
7
-
The sandbox org cloning process %s is in progress. Run "sfdx force:org:status -n %s" to check for status. If the org is ready, checking the status also logs the requesting user in to the sandbox org and authorizes the org for use with Salesforce CLI.
8
-
9
5
# description
10
6
11
7
There are two ways to clone a sandbox: either specify a sandbox definition file or provide key=value pairs at the command line. Key-value pairs at the command-line override their equivalent sandbox definition file values. In either case, you must specify both the "SandboxName" and "SourceSandboxName" options to set the names of the new sandbox and the one being cloned, respectively.
@@ -44,7 +40,7 @@ Sets the streaming client socket timeout, in minutes. If the streaming client so
44
40
45
41
# commandSuccess
46
42
47
-
The sandbox org cloning process %s is in progress. Run "sfdx force:org:status -n %s" to check for status. If the org is ready, checking the status also logs the requesting user in to the sandbox org and authorizes the org for use with Salesforce CLI.
43
+
The sandbox org cloning process %s is in progress. Run "%s force:org:status -n %s" to check for status. If the org is ready, checking the status also logs the requesting user in to the sandbox org and authorizes the org for use with Salesforce CLI.
Copy file name to clipboardExpand all lines: messages/create.md
+4-12Lines changed: 4 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,10 +36,6 @@ Alias for the created org.
36
36
37
37
Path to an org definition file.
38
38
39
-
# flags.definitionJson
40
-
41
-
Org definition in JSON format.
42
-
43
39
# flags.noNamespace
44
40
45
41
Create the scratch org with no namespace.
@@ -48,10 +44,6 @@ Create the scratch org with no namespace.
48
44
49
45
Do not include second-generation package ancestors in the scratch org.
50
46
51
-
# flags.env
52
-
53
-
Environment where the scratch org is created: %s.
54
-
55
47
# flags.type
56
48
57
49
Type of org to create.
@@ -98,19 +90,19 @@ One cannot use flag retry with Sandbox org create.
98
90
99
91
# sandboxSuccess
100
92
101
-
The sandbox org creation process %s is in progress. Run "sfdx force:org:status -n %s -u %s" to check for status. If the org is ready, checking the status also authorizes the org for use with Salesforce CLI.
93
+
The sandbox org creation process %s is in progress. Run "%s force:org:status -n %s -u %s" to check for status. If the org is ready, checking the status also authorizes the org for use with Salesforce CLI.
102
94
103
95
# requiresUsername
104
96
105
-
This command requires a username. Specify it with the -u parameter or with the "sfdx config:set defaultusername=<username>" command.
97
+
This command requires a username. Specify it with the -u parameter or with the "%s configset defaultusername=<username>" command.
106
98
107
99
# dnsTimeout
108
100
109
-
The sandbox was successfully created and authenticated. However, the sandbox DNS records aren't ready yet and so the sandbox may not be available. Run "org:list" and check if the sandbox is listed correctly. If it isn't listed, run "force:org:status" to view its status and, if necessary, authenticate to it again. If this issue happens frequently, try setting the SFDX_DNS_TIMEOUT environment variable to a larger number; the default value is 3 seconds.
101
+
The sandbox was successfully created and authenticated. However, the sandbox DNS records aren't ready yet and so the sandbox may not be available. Run "%s org:list" and check if the sandbox is listed correctly. If it isn't listed, run "%s force:org:status" to view its status and, if necessary, authenticate to it again. If this issue happens frequently, try setting the SFDX_DNS_TIMEOUT environment variable to a larger number; the default value is 3 seconds.
110
102
111
103
# partialSuccess
112
104
113
-
If you specified the -a or -s parameters, but the sandbox wasn't immediately available, the "force:org:create" command may not have finished setting the alias or defaultusername. If so, set the alias manually with "sfdx alias:set" and the defaultusername with "sfdx config:set".
105
+
If you specified the -a or -s parameters, but the sandbox wasn't immediately available, the "%s force:org:create" command may not have finished setting the alias or defaultusername. If so, set the alias manually with "%s alias:set" and the defaultusername with "%s config:set".
If not supplied, the apiversion, template, and outputdir use default values.
4
-
5
-
# HelpOutputDirRelative
6
-
7
-
The outputdir can be an absolute path or relative to the current working directory.
8
-
9
-
# HelpOutputDirRelativeLightning
10
-
11
-
If you don’t specify an outputdir, we create a subfolder in your current working directory with the name of your bundle. For example, if the current working directory is force-app and your Lightning bundle is called myBundle, we create force-app/myBundle/ to store the files in the bundle.
12
-
13
-
# HelpExamplesTitle
14
-
15
-
Examples:
16
-
17
-
# OutputDirFlagDescription
18
-
19
-
folder for saving the created files
20
-
21
-
# OutputDirFlagLongDescription
22
-
23
-
The directory to store the newly created files. The location can be an absolute path or relative to the current working directory. The default is the current directory.
24
-
25
-
# TemplateFlagDescription
26
-
27
-
template to use for file creation
28
-
29
-
# TemplateFlagLongDescription
30
-
31
-
The template to use to create the file. Supplied parameter values or default values are filled into a copy of the template.
32
-
33
-
# TargetDirOutput
34
-
35
-
target dir = %s
36
-
37
-
# App
38
-
39
-
app
40
-
41
-
# Event
42
-
43
-
event
44
-
45
-
# Interface
46
-
47
-
interface
48
-
49
-
# Test
50
-
51
-
test
52
-
53
-
# Component
54
-
55
-
component
56
-
57
-
# Page
58
-
59
-
page
60
-
61
-
# AlphaNumericNameError
62
-
63
-
Name must contain only alphanumeric characters.
64
-
65
-
# NameMustStartWithLetterError
66
-
67
-
Name must start with a letter.
68
-
69
-
# EndWithUnderscoreError
70
-
71
-
Name can't end with an underscore.
72
-
73
-
# DoubleUnderscoreError
74
-
75
-
Name can't contain 2 consecutive underscores.
76
-
77
1
# SecurityWarning
78
2
79
3
This command will expose sensitive information that allows for subsequent activity using your current authenticated session.
80
4
Sharing this information is equivalent to logging someone in under the current credential, resulting in unintended access and escalation of privilege.
81
-
For additional information, please review the authorization section of the https://developer.salesforce.com/docs/atlas.en-us.234.0.sfdx_dev.meta/sfdx_dev/sfdx_dev_auth_web_flow.htm
5
+
For additional information, please review the authorization section of the https://developer.salesforce.com/docs/atlas.en-us.234.0.sfdx_dev.meta/sfdx_dev/sfdx_dev_auth_web_flow.htm
0 commit comments