@peernova/cuneiform-sf 1.0.2 → 1.0.4-beta.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +81 -30
- package/README.md +59 -95
- package/messages/compatibility.check.md +71 -0
- package/messages/cuneiform.access.md +138 -0
- package/messages/definition.create.md +511 -0
- package/messages/definition.export.md +88 -0
- package/messages/definition.get.md +147 -0
- package/messages/definition.import.md +65 -0
- package/messages/definition.list.md +264 -0
- package/messages/definition.purge.md +318 -0
- package/messages/definition.update.md +80 -0
- package/messages/mcp.serve.md +66 -0
- package/messages/object.describe.md +201 -0
- package/messages/object.list.md +443 -0
- package/messages/org.details.md +386 -0
- package/messages/org.reset.md +71 -0
- package/messages/profile.md +231 -0
- package/messages/profile.request.cancel.md +143 -0
- package/messages/profile.request.delete.md +139 -0
- package/messages/profile.request.list.md +89 -0
- package/messages/summary.purge.md +218 -0
- package/messages/summary.reprofile.md +150 -0
- package/messages/summary.stop.md +157 -0
- package/messages/user.details.md +501 -0
- package/oclif.lock +3021 -2224
- package/oclif.manifest.json +2 -116
- package/package.json +84 -19
- package/lib/commands/cuneiform/about.d.ts +0 -13
- package/lib/commands/cuneiform/about.js +0 -26
- package/lib/commands/cuneiform/about.js.map +0 -1
- package/lib/commands/hello/world.d.ts +0 -14
- package/lib/commands/hello/world.js +0 -27
- package/lib/commands/hello/world.js.map +0 -1
- package/lib/index.d.ts +0 -2
- package/lib/index.js +0 -2
- package/lib/index.js.map +0 -1
- package/messages/cuneiform.about.md +0 -19
- package/messages/hello.world.md +0 -29
package/LICENSE
CHANGED
|
@@ -1,36 +1,87 @@
|
|
|
1
|
-
Cuneiform CLI
|
|
1
|
+
Cuneiform for Salesforce CLI — Proprietary Software License
|
|
2
2
|
|
|
3
|
-
Copyright (c)
|
|
3
|
+
Copyright (c) 2026, PeerNova, Inc. All Rights Reserved.
|
|
4
4
|
|
|
5
5
|
TERMS AND CONDITIONS
|
|
6
6
|
|
|
7
|
-
1.
|
|
8
|
-
This software
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
7
|
+
1. PROPRIETARY SOFTWARE
|
|
8
|
+
This software and all associated documentation, source code, and materials
|
|
9
|
+
("Software") are the proprietary and confidential property of PeerNova, Inc.
|
|
10
|
+
This Software is not open source. Access to the source code does not grant
|
|
11
|
+
any license beyond what is expressly stated herein.
|
|
12
12
|
|
|
13
|
-
2.
|
|
13
|
+
2. GRANT OF LICENSE
|
|
14
|
+
Subject to a valid, executed Master Subscription Agreement ("MSA") between
|
|
15
|
+
you (or your organization) and PeerNova, Inc., PeerNova grants you a limited,
|
|
16
|
+
non-exclusive, non-transferable, non-sublicensable license to use this
|
|
17
|
+
Software solely in connection with Cuneiform for Salesforce products and
|
|
18
|
+
services as specified in your MSA.
|
|
19
|
+
|
|
20
|
+
If you do not have a separate written agreement with PeerNova, your use of
|
|
21
|
+
Cuneiform for Salesforce is governed by the terms available at:
|
|
22
|
+
https://peernova.com/legal-cfsf/msa/
|
|
23
|
+
|
|
24
|
+
3. NO LICENSE WITHOUT AGREEMENT
|
|
25
|
+
If you are not a current PeerNova customer with an active MSA, you have no
|
|
26
|
+
right to use, copy, modify, or distribute this Software. If you have received
|
|
27
|
+
access to this Software without an active MSA, you must cease all use
|
|
28
|
+
immediately and contact PeerNova at sfsupport@peernova.com to arrange
|
|
29
|
+
proper licensing.
|
|
30
|
+
|
|
31
|
+
4. RESTRICTIONS
|
|
14
32
|
You may NOT:
|
|
15
|
-
- Modify, adapt, or create derivative works
|
|
16
|
-
- Reverse engineer, decompile, or
|
|
17
|
-
|
|
18
|
-
-
|
|
19
|
-
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
33
|
+
- Modify, adapt, translate, or create derivative works of this Software
|
|
34
|
+
- Reverse engineer, decompile, disassemble, or otherwise attempt to derive
|
|
35
|
+
the source code (except to the extent expressly permitted by applicable law)
|
|
36
|
+
- Remove, alter, or obscure any proprietary notices, labels, or marks
|
|
37
|
+
- Redistribute, sublicense, rent, lease, lend, or transfer this Software
|
|
38
|
+
to any third party
|
|
39
|
+
- Use this Software for any purpose not expressly authorized by your MSA
|
|
40
|
+
- Use this Software to develop competing products or services
|
|
41
|
+
|
|
42
|
+
5. CONFIDENTIALITY
|
|
43
|
+
This Software contains trade secrets and confidential information of
|
|
44
|
+
PeerNova, Inc. You agree to maintain the confidentiality of the Software
|
|
45
|
+
and not disclose it to any third party without PeerNova's prior written
|
|
46
|
+
consent, subject to the terms of your MSA.
|
|
47
|
+
|
|
48
|
+
6. NO WARRANTY
|
|
49
|
+
THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS
|
|
50
|
+
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
51
|
+
FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. PEERNOVA, INC.
|
|
52
|
+
DOES NOT WARRANT THAT THE SOFTWARE WILL MEET YOUR REQUIREMENTS OR THAT
|
|
53
|
+
ITS OPERATION WILL BE UNINTERRUPTED OR ERROR-FREE.
|
|
54
|
+
|
|
55
|
+
7. LIMITATION OF LIABILITY
|
|
56
|
+
IN NO EVENT SHALL PEERNOVA, INC. BE LIABLE FOR ANY INDIRECT, INCIDENTAL,
|
|
57
|
+
SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS,
|
|
58
|
+
REVENUE, DATA, OR DATA USE, ARISING OUT OF OR IN CONNECTION WITH THIS
|
|
59
|
+
SOFTWARE, WHETHER IN AN ACTION OF CONTRACT, TORT, OR OTHERWISE, EVEN IF
|
|
60
|
+
PEERNOVA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. PEERNOVA'S
|
|
61
|
+
TOTAL LIABILITY SHALL NOT EXCEED THE AMOUNTS PAID BY YOU UNDER YOUR MSA
|
|
62
|
+
DURING THE TWELVE (12) MONTHS PRECEDING THE CLAIM.
|
|
63
|
+
|
|
64
|
+
8. TERMINATION
|
|
65
|
+
This license terminates automatically if:
|
|
66
|
+
- You violate any term of this license or your MSA
|
|
67
|
+
- Your MSA expires or is terminated for any reason
|
|
68
|
+
- You fail to maintain an active Cuneiform for Salesforce subscription
|
|
69
|
+
|
|
70
|
+
Upon termination, you must cease all use of the Software and destroy all
|
|
71
|
+
copies in your possession.
|
|
72
|
+
|
|
73
|
+
9. GOVERNING LAW
|
|
74
|
+
This license shall be governed by and construed in accordance with the
|
|
75
|
+
laws specified in your MSA. In the absence of an MSA, the laws of the
|
|
76
|
+
State of California, United States, shall apply.
|
|
77
|
+
|
|
78
|
+
10. ENTIRE AGREEMENT
|
|
79
|
+
This license, together with your MSA, constitutes the entire agreement
|
|
80
|
+
between you and PeerNova, Inc. regarding the Software. In the event of
|
|
81
|
+
any conflict between this license and your MSA, the terms of the MSA
|
|
82
|
+
shall prevail.
|
|
83
|
+
|
|
84
|
+
For licensing inquiries: sfsupport@peernova.com
|
|
85
|
+
For legal questions: legal@peernova.com
|
|
86
|
+
|
|
87
|
+
Master Subscription Agreement: https://peernova.com/legal-cfsf/msa/
|
package/README.md
CHANGED
|
@@ -2,25 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
[](https://www.npmjs.com/package/@peernova/cuneiform-sf) [](https://npmjs.org/package/@peernova/cuneiform-sf) [](https://raw.githubusercontent.com/salesforcecli/@peernova/cuneiform-sf/main/LICENSE.txt)
|
|
4
4
|
|
|
5
|
-
##
|
|
6
|
-
|
|
7
|
-
This repository provides a template for creating a plugin for the Salesforce CLI. To convert this template to a working plugin:
|
|
8
|
-
|
|
9
|
-
1. Please get in touch with the Platform CLI team. We want to help you develop your plugin.
|
|
10
|
-
2. Generate your plugin:
|
|
11
|
-
|
|
12
|
-
```
|
|
13
|
-
sf plugins install dev
|
|
14
|
-
sf dev generate plugin
|
|
15
|
-
|
|
16
|
-
git init -b main
|
|
17
|
-
git add . && git commit -m "chore: initial commit"
|
|
18
|
-
```
|
|
19
|
-
|
|
20
|
-
3. Create your plugin's repo in the salesforcecli github org
|
|
21
|
-
4. When you're ready, replace the contents of this README with the information you want.
|
|
22
|
-
|
|
23
|
-
## Learn about `sf` plugins
|
|
5
|
+
## About
|
|
24
6
|
|
|
25
7
|
Salesforce CLI plugins are based on the [oclif plugin framework](<(https://oclif.io/docs/introduction.html)>). Read the [plugin developer guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_plugins.meta/sfdx_cli_plugins/cli_plugins_architecture_sf_cli.htm) to learn about Salesforce CLI plugin development.
|
|
26
8
|
|
|
@@ -44,11 +26,7 @@ For cross clouds commands, e.g. `sf env list`, we utilize [oclif hooks](https://
|
|
|
44
26
|
|
|
45
27
|
This plugin includes sample hooks in the [src/hooks directory](src/hooks). You'll just need to add the appropriate logic. You can also delete any of the hooks if they aren't required for your plugin.
|
|
46
28
|
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
This plugin is bundled with the [Salesforce CLI](https://developer.salesforce.com/tools/sfdxcli). For more information on the CLI, read the [getting started guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_intro.htm).
|
|
50
|
-
|
|
51
|
-
We always recommend using the latest version of these commands bundled with the CLI, however, you can install a specific version or tag if needed.
|
|
29
|
+
This plugin extends the [Salesforce CLI](https://developer.salesforce.com/tools/sfdxcli) with enterprise data profiling and metadata governance capabilities.
|
|
52
30
|
|
|
53
31
|
## Prerequisites
|
|
54
32
|
|
|
@@ -74,6 +52,48 @@ For more information about SFDMU, visit: https://help.sfdmu.com
|
|
|
74
52
|
sf plugins install @peernova/cuneiform-sf@x.y.z
|
|
75
53
|
```
|
|
76
54
|
|
|
55
|
+
## Compatibility
|
|
56
|
+
|
|
57
|
+
Each CLI release expects a minimum version of the **Cuneiform For Salesforce** managed package (namespace `pnova`) installed in your target org. The required version is published in the CLI's `package.json` under `cuneiform.requiredAppVersion`:
|
|
58
|
+
|
|
59
|
+
```jsonc
|
|
60
|
+
{
|
|
61
|
+
"name": "@peernova/cuneiform-sf",
|
|
62
|
+
"version": "1.0.4-beta.1",
|
|
63
|
+
"cuneiform": {
|
|
64
|
+
"requiredAppVersion": "4.12.0.17"
|
|
65
|
+
}
|
|
66
|
+
}
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
### Check compatibility
|
|
70
|
+
|
|
71
|
+
Print the required app version (no auth, no API calls):
|
|
72
|
+
|
|
73
|
+
```bash
|
|
74
|
+
sf cuneiform compatibility check
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
Verify a target org's installed version:
|
|
78
|
+
|
|
79
|
+
```bash
|
|
80
|
+
sf cuneiform compatibility check --target-org myOrg
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
The command exits non-zero when the installed version is older than required, or when Cuneiform For Salesforce is not installed at all — useful for CI gates that run profiling jobs after a fresh package install.
|
|
84
|
+
|
|
85
|
+
| State | Exit code | Meaning |
|
|
86
|
+
| --------------------------- | :-------: | --------------------------------------------------------------------------------------------------------------- |
|
|
87
|
+
| `installed-match` | 0 | Installed version equals required (Major.Minor.Patch.Build padded) |
|
|
88
|
+
| `installed-newer` | 0 | Installed version is newer than required |
|
|
89
|
+
| `installed-version-unknown` | 0 | Cuneiform detected via namespace but version not exposed (source-pushed scratch orgs, CLI-1569) — cannot verify |
|
|
90
|
+
| `installed-older` | 1 | Installed version is older than required — upgrade the org |
|
|
91
|
+
| `not-installed` | 1 | `pnova` package not installed in the org |
|
|
92
|
+
|
|
93
|
+
### Updating `requiredAppVersion`
|
|
94
|
+
|
|
95
|
+
When releasing a new CLI version that depends on new app-side features, update `cuneiform.requiredAppVersion` in `package.json` alongside the CLI's own `version` bump. The release procedure should treat these as a paired change.
|
|
96
|
+
|
|
77
97
|
## Issues
|
|
78
98
|
|
|
79
99
|
Please report any issues at https://github.com/forcedotcom/cli/issues
|
|
@@ -113,7 +133,7 @@ To use your plugin, run using the local `./bin/dev` or `./bin/dev.cmd` file.
|
|
|
113
133
|
|
|
114
134
|
```bash
|
|
115
135
|
# Run using local run file.
|
|
116
|
-
./bin/dev
|
|
136
|
+
./bin/dev.js cuneiform definition create --help
|
|
117
137
|
```
|
|
118
138
|
|
|
119
139
|
There should be no differences when running via the Salesforce CLI or using the local run file. However, it can be useful to link the plugin to do some additional testing or run your commands from anywhere on your machine.
|
|
@@ -127,77 +147,21 @@ sf plugins
|
|
|
127
147
|
|
|
128
148
|
## Commands
|
|
129
149
|
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
150
|
+
| Command | Description |
|
|
151
|
+
| -------------------------------- | --------------------------------- |
|
|
152
|
+
| `sf cuneiform definition create` | Create profiling definition(s) |
|
|
153
|
+
| `sf cuneiform definition get` | Retrieve profiling definitions |
|
|
154
|
+
| `sf cuneiform definition update` | Update definition field lists |
|
|
155
|
+
| `sf cuneiform definition purge` | Delete unused definitions |
|
|
156
|
+
| `sf cuneiform definition export` | Export definitions (VCS-friendly) |
|
|
157
|
+
| `sf cuneiform definition import` | Import definitions from export |
|
|
158
|
+
| `sf cuneiform profile` | Execute profiling operations |
|
|
136
159
|
|
|
137
|
-
|
|
160
|
+
For detailed usage, run any command with `--help`:
|
|
138
161
|
|
|
162
|
+
```bash
|
|
163
|
+
sf cuneiform definition create --help
|
|
164
|
+
sf cuneiform profile --help
|
|
139
165
|
```
|
|
140
|
-
USAGE
|
|
141
|
-
$ sf cuneiform about [--json] [--flags-dir <value>] [-n <value>]
|
|
142
|
-
|
|
143
|
-
FLAGS
|
|
144
|
-
-n, --name=<value> Description of a flag.
|
|
145
|
-
|
|
146
|
-
GLOBAL FLAGS
|
|
147
|
-
--flags-dir=<value> Import flag values from a directory.
|
|
148
|
-
--json Format output as json.
|
|
149
|
-
|
|
150
|
-
DESCRIPTION
|
|
151
|
-
Summary of a command.
|
|
152
|
-
|
|
153
|
-
More information about a command. Don't repeat the summary.
|
|
154
|
-
|
|
155
|
-
EXAMPLES
|
|
156
|
-
$ sf cuneiform about
|
|
157
|
-
|
|
158
|
-
FLAG DESCRIPTIONS
|
|
159
|
-
-n, --name=<value> Description of a flag.
|
|
160
|
-
|
|
161
|
-
More information about a flag. Don't repeat the summary.
|
|
162
|
-
```
|
|
163
|
-
|
|
164
|
-
_See code: [src/commands/cuneiform/about.ts](https://github.com/PeerNova-Solutions/cuneiform-cli/blob/1.0.2/src/commands/cuneiform/about.ts)_
|
|
165
|
-
|
|
166
|
-
## `sf hello world`
|
|
167
|
-
|
|
168
|
-
Say hello.
|
|
169
|
-
|
|
170
|
-
```
|
|
171
|
-
USAGE
|
|
172
|
-
$ sf hello world [--json] [--flags-dir <value>] [-n <value>]
|
|
173
|
-
|
|
174
|
-
FLAGS
|
|
175
|
-
-n, --name=<value> [default: World] The name of the person you'd like to say hello to.
|
|
176
|
-
|
|
177
|
-
GLOBAL FLAGS
|
|
178
|
-
--flags-dir=<value> Import flag values from a directory.
|
|
179
|
-
--json Format output as json.
|
|
180
|
-
|
|
181
|
-
DESCRIPTION
|
|
182
|
-
Say hello.
|
|
183
|
-
|
|
184
|
-
Say hello either to the world or someone you know.
|
|
185
|
-
|
|
186
|
-
EXAMPLES
|
|
187
|
-
Say hello to the world:
|
|
188
|
-
|
|
189
|
-
$ sf hello world
|
|
190
|
-
|
|
191
|
-
Say hello to someone you know:
|
|
192
|
-
|
|
193
|
-
$ sf hello world --name Astro
|
|
194
|
-
|
|
195
|
-
FLAG DESCRIPTIONS
|
|
196
|
-
-n, --name=<value> The name of the person you'd like to say hello to.
|
|
197
|
-
|
|
198
|
-
This person can be anyone in the world!
|
|
199
|
-
```
|
|
200
|
-
|
|
201
|
-
_See code: [src/commands/hello/world.ts](https://github.com/PeerNova-Solutions/cuneiform-cli/blob/1.0.2/src/commands/hello/world.ts)_
|
|
202
166
|
|
|
203
|
-
|
|
167
|
+
# Test run for workflow verification
|
|
@@ -0,0 +1,71 @@
|
|
|
1
|
+
# summary
|
|
2
|
+
|
|
3
|
+
Verify the Cuneiform For Salesforce app version required by this CLI build, and (optionally) the version installed in a target org.
|
|
4
|
+
|
|
5
|
+
# description
|
|
6
|
+
|
|
7
|
+
Reports the Cuneiform For Salesforce managed-package version this CLI release was tested against. Without `--target-org`, the command is a local-only readout — no Salesforce API calls, no authentication required.
|
|
8
|
+
|
|
9
|
+
When `--target-org` is supplied, the command queries the org for the installed Cuneiform For Salesforce package via the Tooling API and reports one of five states:
|
|
10
|
+
|
|
11
|
+
- `installed-match` — installed version satisfies the requirement (exit 0)
|
|
12
|
+
- `installed-newer` — installed version is newer than required (exit 0, advisory)
|
|
13
|
+
- `installed-version-unknown` — Cuneiform is detected via namespace but the version is not exposed (typical for source-pushed scratch orgs — CLI-1569). Compatibility cannot be verified, but the package is present (exit 0, advisory)
|
|
14
|
+
- `installed-older` — installed version is older than required (exit 1)
|
|
15
|
+
- `not-installed` — Cuneiform For Salesforce is not installed in this org (exit 1)
|
|
16
|
+
|
|
17
|
+
Use this command to:
|
|
18
|
+
|
|
19
|
+
- Confirm a scratch org or sandbox is ready for CLI operations after a fresh package install
|
|
20
|
+
- Diagnose CLI errors that look like data-shape mismatches but are version-compatibility issues
|
|
21
|
+
- Pin CLI/app version pairs in CI before running profiling jobs
|
|
22
|
+
|
|
23
|
+
# examples
|
|
24
|
+
|
|
25
|
+
- Print the required app version (no auth, no API calls):
|
|
26
|
+
|
|
27
|
+
<%= config.bin %> <%= command.id %>
|
|
28
|
+
|
|
29
|
+
- Verify the installed version in a target org:
|
|
30
|
+
|
|
31
|
+
<%= config.bin %> <%= command.id %> --target-org myOrg
|
|
32
|
+
|
|
33
|
+
- Machine-readable output for CI:
|
|
34
|
+
|
|
35
|
+
<%= config.bin %> <%= command.id %> --target-org myOrg --json
|
|
36
|
+
|
|
37
|
+
# flags.target-org.summary
|
|
38
|
+
|
|
39
|
+
Target org username or alias. When supplied, the command queries the org's installed Cuneiform For Salesforce version and reports compatibility.
|
|
40
|
+
|
|
41
|
+
# flags.api-version.summary
|
|
42
|
+
|
|
43
|
+
API version to use when querying the target org. Defaults to the org's maximum supported version.
|
|
44
|
+
|
|
45
|
+
# state.installed-match
|
|
46
|
+
|
|
47
|
+
✓ Installed version matches the required version. Compatible.
|
|
48
|
+
|
|
49
|
+
# state.installed-newer
|
|
50
|
+
|
|
51
|
+
✓ Installed version is newer than required. Likely compatible — newer org-side features may not be exposed by this CLI build.
|
|
52
|
+
|
|
53
|
+
# state.installed-version-unknown
|
|
54
|
+
|
|
55
|
+
⚠ Cuneiform For Salesforce is present in this org (detected via namespace) but the package version is not exposed by the standard API. This is typical for source-pushed scratch orgs. Compatibility cannot be verified against the requirement — proceed at your own risk.
|
|
56
|
+
|
|
57
|
+
# state.installed-older
|
|
58
|
+
|
|
59
|
+
✗ Installed version is older than required. CLI commands that depend on newer app features will fail. Upgrade Cuneiform For Salesforce in this org to at least the required version.
|
|
60
|
+
|
|
61
|
+
# state.not-installed
|
|
62
|
+
|
|
63
|
+
✗ Cuneiform For Salesforce is not installed in this org. Install the managed package before running CLI commands.
|
|
64
|
+
|
|
65
|
+
# errors.manifestInvalid
|
|
66
|
+
|
|
67
|
+
This CLI build's `package.json` is missing the `cuneiform.requiredAppVersion` field. This is a build-time configuration error — please file an issue on the salesforce-cli repository.
|
|
68
|
+
|
|
69
|
+
# errors.orgQueryFailed
|
|
70
|
+
|
|
71
|
+
Failed to query the installed package version from the target org: %s
|
|
@@ -0,0 +1,138 @@
|
|
|
1
|
+
# error.profilingAccessDenied
|
|
2
|
+
|
|
3
|
+
Cuneiform is installed, but you don't have profiling access.
|
|
4
|
+
|
|
5
|
+
You're missing one or more required permission sets.
|
|
6
|
+
|
|
7
|
+
Next steps:
|
|
8
|
+
|
|
9
|
+
1. Run the diagnostic to see exactly what's missing:
|
|
10
|
+
sf cuneiform user details --target-org <your-org>
|
|
11
|
+
|
|
12
|
+
2. Preview what the auto-configure would change:
|
|
13
|
+
sf cuneiform user details --target-org <your-org> --configure --dry-run
|
|
14
|
+
|
|
15
|
+
3. Apply the changes automatically:
|
|
16
|
+
sf cuneiform user details --target-org <your-org> --configure
|
|
17
|
+
|
|
18
|
+
If you don't have permission to self-configure, ask your Salesforce administrator to assign the required Cuneiform permission sets.
|
|
19
|
+
|
|
20
|
+
# error.globalProfilingNotEnabled
|
|
21
|
+
|
|
22
|
+
Cuneiform is installed, but Global Profiling is not enabled.
|
|
23
|
+
|
|
24
|
+
API-Only Profiling must be enabled in the Configuration Profile before you can use the CLI.
|
|
25
|
+
|
|
26
|
+
Next steps:
|
|
27
|
+
|
|
28
|
+
1. Run the diagnostic to see your current readiness:
|
|
29
|
+
sf cuneiform user details --target-org <your-org>
|
|
30
|
+
|
|
31
|
+
2. Preview what the auto-configure would change:
|
|
32
|
+
sf cuneiform user details --target-org <your-org> --configure --dry-run
|
|
33
|
+
|
|
34
|
+
3. Apply the changes automatically:
|
|
35
|
+
sf cuneiform user details --target-org <your-org> --configure
|
|
36
|
+
|
|
37
|
+
If you don't have permission to self-configure, ask your Salesforce administrator to enable API-Only Profiling in the Cuneiform Configuration Profile.
|
|
38
|
+
|
|
39
|
+
# error.cuneiformNotInstalled
|
|
40
|
+
|
|
41
|
+
Cuneiform for Salesforce is not installed in this org.
|
|
42
|
+
|
|
43
|
+
The Cuneiform for Salesforce CLI is available exclusively to PeerNova customers with an active license. The managed package must be installed and activated before you can use the CLI.
|
|
44
|
+
|
|
45
|
+
Next steps:
|
|
46
|
+
|
|
47
|
+
1. If you are a PeerNova customer, contact your Salesforce administrator to install the package.
|
|
48
|
+
|
|
49
|
+
2. If you need to obtain a license, request one at:
|
|
50
|
+
https://jira-peernova.atlassian.net/wiki/spaces/CFCPD/pages/4196499551
|
|
51
|
+
|
|
52
|
+
3. To get Cuneiform for Salesforce:
|
|
53
|
+
https://jira-peernova.atlassian.net/wiki/spaces/CFCPD/pages/2624356353
|
|
54
|
+
|
|
55
|
+
4. Once installed, verify your readiness:
|
|
56
|
+
sf cuneiform user details --target-org <your-org>
|
|
57
|
+
|
|
58
|
+
For help: sfsupport@peernova.com
|
|
59
|
+
|
|
60
|
+
# error.selfRegistrationNotEnabled
|
|
61
|
+
|
|
62
|
+
Cuneiform is installed and API-Only Profiling is enabled, but CLI self-provisioning is not available.
|
|
63
|
+
|
|
64
|
+
Your administrator has not enabled CLI self-provisioning for API-based profiling. This setting ensures your admin controls which users can configure their own API profiling access — you're one admin action away from full access.
|
|
65
|
+
|
|
66
|
+
Next steps:
|
|
67
|
+
|
|
68
|
+
1. Run the diagnostic to see your full readiness status:
|
|
69
|
+
sf cuneiform user details --target-org <your-org>
|
|
70
|
+
|
|
71
|
+
2. Ask your Salesforce administrator to enable "Enable API Profiling Self-Registration"
|
|
72
|
+
in the Cuneiform Configuration Profile (Custom Metadata).
|
|
73
|
+
|
|
74
|
+
3. Alternatively, your admin can assign the API-Based Profiling permission set to you
|
|
75
|
+
directly, bypassing self-provisioning.
|
|
76
|
+
|
|
77
|
+
# error.featureNotEnabled
|
|
78
|
+
|
|
79
|
+
API-Based Profiling is not enabled for this organization.
|
|
80
|
+
|
|
81
|
+
The Cuneiform for Salesforce CLI is available exclusively to PeerNova customers with an active license. This feature must be enabled by PeerNova before you can use the CLI.
|
|
82
|
+
|
|
83
|
+
Next steps:
|
|
84
|
+
|
|
85
|
+
1. If you are a PeerNova customer, contact your PeerNova account team to enable
|
|
86
|
+
API-Based Profiling for your organization.
|
|
87
|
+
|
|
88
|
+
2. If you need to obtain a license, request one at:
|
|
89
|
+
https://jira-peernova.atlassian.net/wiki/spaces/CFCPD/pages/4196499551
|
|
90
|
+
|
|
91
|
+
3. To get Cuneiform for Salesforce:
|
|
92
|
+
https://jira-peernova.atlassian.net/wiki/spaces/CFCPD/pages/2624356353
|
|
93
|
+
|
|
94
|
+
4. Once enabled, verify your readiness:
|
|
95
|
+
sf cuneiform user details --target-org <your-org>
|
|
96
|
+
|
|
97
|
+
For help: sfsupport@peernova.com
|
|
98
|
+
|
|
99
|
+
# error.environmentConfigureBlocked
|
|
100
|
+
|
|
101
|
+
Configuration is not allowed in production environments.
|
|
102
|
+
|
|
103
|
+
The configure and autoconfigure commands are restricted to non-production orgs to protect your production data. This org has been identified as a Production org.
|
|
104
|
+
|
|
105
|
+
Next steps:
|
|
106
|
+
|
|
107
|
+
1. Run the diagnostic to confirm your org type:
|
|
108
|
+
sf cuneiform user details --target-org <your-org>
|
|
109
|
+
|
|
110
|
+
2. Use a sandbox, scratch org, or developer org to test configuration:
|
|
111
|
+
sf cuneiform user details --target-org <sandbox-org> --configure
|
|
112
|
+
|
|
113
|
+
3. If you believe this org was misidentified, contact your Salesforce administrator to verify the org type.
|
|
114
|
+
|
|
115
|
+
# error.connectionFailed
|
|
116
|
+
|
|
117
|
+
Could not verify your Cuneiform access. The connection to your org failed before the access check could run.
|
|
118
|
+
|
|
119
|
+
Detail: %s
|
|
120
|
+
|
|
121
|
+
Next steps:
|
|
122
|
+
|
|
123
|
+
1. Verify your org is authenticated:
|
|
124
|
+
sf org list --all
|
|
125
|
+
|
|
126
|
+
2. Re-authenticate if needed:
|
|
127
|
+
sf org login web --alias <your-org>
|
|
128
|
+
|
|
129
|
+
3. Once connected, verify your readiness:
|
|
130
|
+
sf cuneiform user details --target-org <your-org>
|
|
131
|
+
|
|
132
|
+
If the problem persists, check your network connection and ensure the Salesforce instance is reachable.
|
|
133
|
+
|
|
134
|
+
# error.accessCheckFailed
|
|
135
|
+
|
|
136
|
+
Could not verify your Cuneiform access.
|
|
137
|
+
|
|
138
|
+
%s
|