@heroku/plugin-compute 0.3.1 → 0.4.0
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/{lib → dist}/commands/compute/create/telemetry-drain.d.ts +1 -0
- package/{lib → dist}/commands/compute/create/telemetry-drain.js +2 -1
- package/{lib → dist}/commands/compute/create/telemetry-drain.js.map +1 -1
- package/dist/commands/compute/delete/telemetry-drain.d.ts +20 -0
- package/dist/commands/compute/delete/telemetry-drain.js +60 -0
- package/dist/commands/compute/delete/telemetry-drain.js.map +1 -0
- package/dist/commands/compute/deploy.d.ts +12 -0
- package/dist/commands/compute/deploy.js +37 -0
- package/dist/commands/compute/deploy.js.map +1 -0
- package/{lib → dist}/commands/compute/display/telemetry-drain.d.ts +1 -0
- package/{lib → dist}/commands/compute/display/telemetry-drain.js +4 -3
- package/dist/commands/compute/display/telemetry-drain.js.map +1 -0
- package/{lib → dist}/commands/compute/display.d.ts +1 -0
- package/{lib → dist}/commands/compute/display.js +2 -1
- package/dist/commands/compute/display.js.map +1 -0
- package/{lib → dist}/commands/compute/generate.js +4 -4
- package/{lib → dist}/commands/compute/generate.js.map +1 -1
- package/{lib → dist}/commands/compute/get/build-log.d.ts +1 -0
- package/{lib → dist}/commands/compute/get/build-log.js +2 -1
- package/dist/commands/compute/get/build-log.js.map +1 -0
- package/{lib → dist}/commands/compute/get/config.d.ts +1 -0
- package/{lib → dist}/commands/compute/get/config.js +2 -1
- package/dist/commands/compute/get/config.js.map +1 -0
- package/{lib → dist}/commands/compute/get/runtime-log.d.ts +1 -0
- package/{lib → dist}/commands/compute/get/runtime-log.js +14 -3
- package/dist/commands/compute/get/runtime-log.js.map +1 -0
- package/{lib → dist}/commands/compute/list/config.d.ts +1 -0
- package/{lib → dist}/commands/compute/list/config.js +2 -1
- package/dist/commands/compute/list/config.js.map +1 -0
- package/{lib → dist}/commands/compute/list/telemetry-drain.d.ts +1 -0
- package/{lib → dist}/commands/compute/list/telemetry-drain.js +2 -1
- package/{lib → dist}/commands/compute/list/telemetry-drain.js.map +1 -1
- package/{lib → dist}/commands/compute/list.d.ts +1 -0
- package/{lib → dist}/commands/compute/list.js +2 -1
- package/dist/commands/compute/list.js.map +1 -0
- package/{lib → dist}/commands/compute/scale.d.ts +1 -0
- package/{lib → dist}/commands/compute/scale.js +2 -1
- package/dist/commands/compute/scale.js.map +1 -0
- package/{lib → dist}/commands/compute/set/config.d.ts +1 -0
- package/{lib → dist}/commands/compute/set/config.js +2 -1
- package/dist/commands/compute/set/config.js.map +1 -0
- package/{lib → dist}/commands/compute/source/retrieve.d.ts +1 -0
- package/{lib → dist}/commands/compute/source/retrieve.js +5 -6
- package/dist/commands/compute/source/retrieve.js.map +1 -0
- package/{lib → dist}/commands/compute/tail/runtime-log.d.ts +1 -0
- package/{lib → dist}/commands/compute/tail/runtime-log.js +22 -6
- package/dist/commands/compute/tail/runtime-log.js.map +1 -0
- package/{lib → dist}/commands/compute/unset/config.d.ts +1 -0
- package/{lib → dist}/commands/compute/unset/config.js +2 -1
- package/dist/commands/compute/unset/config.js.map +1 -0
- package/{lib → dist}/commands/compute/update/telemetry-drain.d.ts +1 -0
- package/{lib → dist}/commands/compute/update/telemetry-drain.js +2 -1
- package/dist/commands/compute/update/telemetry-drain.js.map +1 -0
- package/{lib → dist}/shared/computeApp.js +1 -1
- package/{lib → dist}/shared/computeApp.js.map +1 -1
- package/{lib → dist}/shared/computeBundle.js +1 -1
- package/{lib → dist}/shared/computeBundle.js.map +1 -1
- package/{lib → dist}/shared/computeGenerateSkeletons.js +4 -2
- package/{lib → dist}/shared/computeGenerateSkeletons.js.map +1 -1
- package/{lib → dist}/shared/computeLogStream.d.ts +6 -1
- package/{lib → dist}/shared/computeLogStream.js +30 -3
- package/dist/shared/computeLogStream.js.map +1 -0
- package/{lib → dist}/shared/computeTelemetryDrain.d.ts +1 -0
- package/{lib → dist}/shared/computeTelemetryDrain.js +5 -8
- package/dist/shared/computeTelemetryDrain.js.map +1 -0
- package/{lib → dist}/shared/metadataApiVersion.js +1 -1
- package/{lib → dist}/shared/metadataApiVersion.js.map +1 -1
- package/{lib → dist}/shared/metadataDeploy.js +8 -8
- package/dist/shared/metadataDeploy.js.map +1 -0
- package/{lib → dist}/shared/metadataRetrieve.js +12 -8
- package/dist/shared/metadataRetrieve.js.map +1 -0
- package/messages/compute.create.telemetry-drain.md +1 -1
- package/messages/compute.delete.telemetry-drain.md +41 -0
- package/messages/compute.deploy.md +12 -70
- package/messages/compute.display.telemetry-drain.md +1 -0
- package/messages/compute.errors.md +16 -6
- package/messages/compute.generate.md +3 -3
- package/messages/compute.get.runtime-log.md +19 -0
- package/messages/compute.source.retrieve.md +4 -4
- package/messages/compute.update.telemetry-drain.md +1 -1
- package/npm-shrinkwrap.json +441 -854
- package/oclif.manifest.json +225 -42
- package/package.json +19 -18
- package/schemas/compute-delete-telemetry__drain.json +22 -0
- package/lib/commands/compute/deploy.d.ts +0 -18
- package/lib/commands/compute/deploy.js +0 -95
- package/lib/commands/compute/deploy.js.map +0 -1
- package/lib/commands/compute/display/telemetry-drain.js.map +0 -1
- package/lib/commands/compute/display.js.map +0 -1
- package/lib/commands/compute/get/build-log.js.map +0 -1
- package/lib/commands/compute/get/config.js.map +0 -1
- package/lib/commands/compute/get/runtime-log.js.map +0 -1
- package/lib/commands/compute/list/config.js.map +0 -1
- package/lib/commands/compute/list.js.map +0 -1
- package/lib/commands/compute/scale.js.map +0 -1
- package/lib/commands/compute/set/config.js.map +0 -1
- package/lib/commands/compute/source/retrieve.js.map +0 -1
- package/lib/commands/compute/tail/runtime-log.js.map +0 -1
- package/lib/commands/compute/unset/config.js.map +0 -1
- package/lib/commands/compute/update/telemetry-drain.js.map +0 -1
- package/lib/shared/computeLogStream.js.map +0 -1
- package/lib/shared/computeTelemetryDrain.js.map +0 -1
- package/lib/shared/metadataDeploy.js.map +0 -1
- package/lib/shared/metadataRetrieve.js.map +0 -1
- package/schemas/compute-deploy.json +0 -30
- /package/{lib → dist}/commands/compute/generate.d.ts +0 -0
- /package/{lib → dist}/index.d.ts +0 -0
- /package/{lib → dist}/index.js +0 -0
- /package/{lib → dist}/index.js.map +0 -0
- /package/{lib → dist}/shared/computeApp.d.ts +0 -0
- /package/{lib → dist}/shared/computeBundle.d.ts +0 -0
- /package/{lib → dist}/shared/computeConfig.d.ts +0 -0
- /package/{lib → dist}/shared/computeConfig.js +0 -0
- /package/{lib → dist}/shared/computeConfig.js.map +0 -0
- /package/{lib → dist}/shared/computeConnectApi.d.ts +0 -0
- /package/{lib → dist}/shared/computeConnectApi.js +0 -0
- /package/{lib → dist}/shared/computeConnectApi.js.map +0 -0
- /package/{lib → dist}/shared/computeGenerateSkeletons.d.ts +0 -0
- /package/{lib → dist}/shared/computeGenerateSource.d.ts +0 -0
- /package/{lib → dist}/shared/computeGenerateSource.js +0 -0
- /package/{lib → dist}/shared/computeGenerateSource.js.map +0 -0
- /package/{lib → dist}/shared/computeQuery.d.ts +0 -0
- /package/{lib → dist}/shared/computeQuery.js +0 -0
- /package/{lib → dist}/shared/computeQuery.js.map +0 -0
- /package/{lib → dist}/shared/herokuProxyApi.d.ts +0 -0
- /package/{lib → dist}/shared/herokuProxyApi.js +0 -0
- /package/{lib → dist}/shared/herokuProxyApi.js.map +0 -0
- /package/{lib → dist}/shared/metadataApiVersion.d.ts +0 -0
- /package/{lib → dist}/shared/metadataDeploy.d.ts +0 -0
- /package/{lib → dist}/shared/metadataRetrieve.d.ts +0 -0
- /package/{lib → dist}/shared/plugin-name.d.ts +0 -0
- /package/{lib → dist}/shared/plugin-name.js +0 -0
- /package/{lib → dist}/shared/plugin-name.js.map +0 -0
|
@@ -16,7 +16,7 @@
|
|
|
16
16
|
import { getLogger } from '@oclif/core';
|
|
17
17
|
import { Messages } from '@salesforce/core';
|
|
18
18
|
import JSZip from 'jszip';
|
|
19
|
-
import { writeFile } from 'node:fs/promises';
|
|
19
|
+
import { mkdir, writeFile } from 'node:fs/promises';
|
|
20
20
|
import { join } from 'node:path';
|
|
21
21
|
import { resolveComputeApiVersion } from './metadataApiVersion.js';
|
|
22
22
|
import { PLUGIN_NAME } from './plugin-name.js';
|
|
@@ -26,7 +26,7 @@ const messages = Messages.loadMessages(PLUGIN_NAME, 'compute.errors');
|
|
|
26
26
|
const { debug } = getLogger('sf:compute:metadataRetrieve');
|
|
27
27
|
// Inverse of deployComputeMetadata in metadataDeploy.ts, but NOT built on SDR's
|
|
28
28
|
// ComponentSet/MetadataApiRetrieve the way that function is built on MetadataApiDeploy --
|
|
29
|
-
//
|
|
29
|
+
// ComputeApp has no entry in SDR's metadata registry, and ComponentSet.getObject()
|
|
30
30
|
// (called internally when building a retrieve request) requires resolving every member's type
|
|
31
31
|
// against that registry, so it throws for this type today. This uses jsforce's lower-level
|
|
32
32
|
// retrieve API directly instead. Note the asymmetry with deployComputeMetadata's
|
|
@@ -38,7 +38,7 @@ export async function retrieveComputeMetadata(connection, appDir, name) {
|
|
|
38
38
|
apiVersion: Number(version),
|
|
39
39
|
singlePackage: true,
|
|
40
40
|
unpackaged: {
|
|
41
|
-
types: [{ members: [name], name: '
|
|
41
|
+
types: [{ members: [name], name: 'ComputeApp' }],
|
|
42
42
|
version,
|
|
43
43
|
// Package requires objectPermissions -- retrieve doesn't use it, but the type isn't
|
|
44
44
|
// Partial<Package> the way the outer RetrieveRequest is Partial<RetrieveRequest>.
|
|
@@ -53,16 +53,20 @@ export async function retrieveComputeMetadata(connection, appDir, name) {
|
|
|
53
53
|
}
|
|
54
54
|
const zip = await JSZip.loadAsync(result.zipFile, { base64: true });
|
|
55
55
|
// Wire directoryName/suffix -- see the matching comment in metadataDeploy.ts. Our own on-disk
|
|
56
|
-
// source-format filename (<name>.
|
|
57
|
-
const wireFileName = `${name}.
|
|
58
|
-
const metaFileName = `${name}.
|
|
59
|
-
const metaEntry = zip.file(`
|
|
56
|
+
// source-format filename (<name>.computeApp-meta.xml) is independent of the wire filename.
|
|
57
|
+
const wireFileName = `${name}.computeApp`;
|
|
58
|
+
const metaFileName = `${name}.computeApp-meta.xml`;
|
|
59
|
+
const metaEntry = zip.file(`computeApps/${wireFileName}`);
|
|
60
60
|
if (!metaEntry) {
|
|
61
|
+
// An unknown type doesn't fail the retrieve -- it only adds a warning to result.messages.
|
|
62
|
+
const problems = [result.messages ?? []].flat().map(m => m.problem);
|
|
63
|
+
const problemDetail = problems.length > 0 ? ` (${problems.join('; ')})` : '';
|
|
61
64
|
throw messages.createError('error.metadataRetrieveFailed', [
|
|
62
65
|
name,
|
|
63
|
-
`the retrieved metadata is missing
|
|
66
|
+
`the retrieved metadata is missing computeApps/${wireFileName}${problemDetail}`,
|
|
64
67
|
]);
|
|
65
68
|
}
|
|
69
|
+
await mkdir(appDir, { recursive: true });
|
|
66
70
|
await writeFile(join(appDir, metaFileName), await metaEntry.async('nodebuffer'));
|
|
67
71
|
}
|
|
68
72
|
//# sourceMappingURL=metadataRetrieve.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"metadataRetrieve.js","sourceRoot":"","sources":["../../src/shared/metadataRetrieve.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAEH,OAAO,EAAC,SAAS,EAAC,MAAM,aAAa,CAAC;AACtC,OAAO,EAAkB,QAAQ,EAAC,MAAM,kBAAkB,CAAC;AAC3D,OAAO,KAAK,MAAM,OAAO,CAAC;AAC1B,OAAO,EAAC,KAAK,EAAE,SAAS,EAAC,MAAM,kBAAkB,CAAC;AAClD,OAAO,EAAC,IAAI,EAAC,MAAM,WAAW,CAAC;AAE/B,OAAO,EAAC,wBAAwB,EAAC,MAAM,yBAAyB,CAAC;AACjE,OAAO,EAAC,WAAW,EAAC,MAAM,kBAAkB,CAAC;AAE7C,QAAQ,CAAC,kCAAkC,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;AAC7D,MAAM,QAAQ,GAAG,QAAQ,CAAC,YAAY,CAAC,WAAW,EAAE,gBAAgB,CAAC,CAAC;AAEtE,2DAA2D;AAC3D,MAAM,EAAC,KAAK,EAAC,GAAG,SAAS,CAAC,6BAA6B,CAAC,CAAC;AAEzD,gFAAgF;AAChF,0FAA0F;AAC1F,mFAAmF;AACnF,8FAA8F;AAC9F,2FAA2F;AAC3F,iFAAiF;AACjF,0FAA0F;AAC1F,6FAA6F;AAC7F,MAAM,CAAC,KAAK,UAAU,uBAAuB,CAAC,UAAsB,EAAE,MAAc,EAAE,IAAY;IAChG,MAAM,OAAO,GAAG,wBAAwB,CAAC,UAAU,CAAC,CAAC;IACrD,MAAM,cAAc,GAAG,UAAU,CAAC,QAAQ,CAAC,QAAQ,CAAC;QAClD,UAAU,EAAE,MAAM,CAAC,OAAO,CAAC;QAC3B,aAAa,EAAE,IAAI;QACnB,UAAU,EAAE;YACV,KAAK,EAAE,CAAC,EAAC,OAAO,EAAE,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,YAAY,EAAC,CAAC;YAC9C,OAAO;YACP,oFAAoF;YACpF,kFAAkF;YAClF,iBAAiB,EAAE,EAAE;SACtB;KACF,CAAC,CAAC;IACH,KAAK,CAAC,0CAA0C,EAAE,IAAI,EAAE,UAAU,CAAC,WAAW,EAAE,IAAI,OAAO,CAAC,CAAC;IAC7F,MAAM,MAAM,GAAG,MAAM,cAAc,CAAC,QAAQ,EAAE,CAAC;IAC/C,KAAK,CAAC,+CAA+C,EAAE,IAAI,EAAE,MAAM,CAAC,OAAO,CAAC,CAAC;IAE7E,IAAI,CAAC,MAAM,CAAC,OAAO,EAAE,CAAC;QACpB,MAAM,QAAQ,CAAC,WAAW,CAAC,8BAA8B,EAAE,CAAC,IAAI,EAAE,MAAM,CAAC,YAAY,IAAI,gBAAgB,CAAC,CAAC,CAAC;IAC9G,CAAC;IAED,MAAM,GAAG,GAAG,MAAM,KAAK,CAAC,SAAS,CAAC,MAAM,CAAC,OAAO,EAAE,EAAC,MAAM,EAAE,IAAI,EAAC,CAAC,CAAC;IAClE,8FAA8F;IAC9F,2FAA2F;IAC3F,MAAM,YAAY,GAAG,GAAG,IAAI,aAAa,CAAC;IAC1C,MAAM,YAAY,GAAG,GAAG,IAAI,sBAAsB,CAAC;IACnD,MAAM,SAAS,GAAG,GAAG,CAAC,IAAI,CAAC,eAAe,YAAY,EAAE,CAAC,CAAC;IAC1D,IAAI,CAAC,SAAS,EAAE,CAAC;QACf,0FAA0F;QAC1F,MAAM,QAAQ,GAAG,CAAC,MAAM,CAAC,QAAQ,IAAI,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,CAAC;QACpE,MAAM,aAAa,GAAG,QAAQ,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,KAAK,QAAQ,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC;QAC7E,MAAM,QAAQ,CAAC,WAAW,CAAC,8BAA8B,EAAE;YACzD,IAAI;YACJ,iDAAiD,YAAY,GAAG,aAAa,EAAE;SAChF,CAAC,CAAC;IACL,CAAC;IAED,MAAM,KAAK,CAAC,MAAM,EAAE,EAAC,SAAS,EAAE,IAAI,EAAC,CAAC,CAAC;IACvC,MAAM,SAAS,CAAC,IAAI,CAAC,MAAM,EAAE,YAAY,CAAC,EAAE,MAAM,SAAS,CAAC,KAAK,CAAC,YAAY,CAAC,CAAC,CAAC;AACnF,CAAC"}
|
|
@@ -36,7 +36,7 @@ Header to send with each export, as key=value.
|
|
|
36
36
|
|
|
37
37
|
Repeat the flag to send more than one header. Header values often carry
|
|
38
38
|
credentials; they are sent to the endpoint and are never printed to the
|
|
39
|
-
terminal
|
|
39
|
+
terminal or --json output; header keys are preserved with redacted values.
|
|
40
40
|
|
|
41
41
|
# info.created
|
|
42
42
|
|
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
# summary
|
|
2
|
+
|
|
3
|
+
Delete a compute telemetry drain.
|
|
4
|
+
|
|
5
|
+
# description
|
|
6
|
+
|
|
7
|
+
Removes a single OpenTelemetry drain by its ID, so its compute app stops
|
|
8
|
+
forwarding logs, metrics, and traces to the drain's endpoint. This can't be
|
|
9
|
+
undone; to forward telemetry again, create a new drain. You're asked to
|
|
10
|
+
confirm first unless you pass --no-prompt. Use sf compute list telemetry-drain
|
|
11
|
+
to find a drain's ID.
|
|
12
|
+
|
|
13
|
+
# args.id.summary
|
|
14
|
+
|
|
15
|
+
ID of the telemetry drain to delete.
|
|
16
|
+
|
|
17
|
+
# flags.no-prompt.summary
|
|
18
|
+
|
|
19
|
+
Don't ask for confirmation before deleting.
|
|
20
|
+
|
|
21
|
+
# info.confirm
|
|
22
|
+
|
|
23
|
+
Delete telemetry drain %s? This stops forwarding telemetry to its endpoint.
|
|
24
|
+
|
|
25
|
+
# info.aborted
|
|
26
|
+
|
|
27
|
+
Telemetry drain %s was not deleted.
|
|
28
|
+
|
|
29
|
+
# info.deleted
|
|
30
|
+
|
|
31
|
+
Deleted telemetry drain %s.
|
|
32
|
+
|
|
33
|
+
# examples
|
|
34
|
+
|
|
35
|
+
- Delete a telemetry drain, confirming first:
|
|
36
|
+
|
|
37
|
+
<%= config.bin %> <%= command.id %> 01234567-89ab-cdef-0123-456789abcdef --target-org my-org
|
|
38
|
+
|
|
39
|
+
- Delete a telemetry drain without the confirmation prompt, for scripts:
|
|
40
|
+
|
|
41
|
+
<%= config.bin %> <%= command.id %> 01234567-89ab-cdef-0123-456789abcdef --target-org my-org --no-prompt
|
|
@@ -1,84 +1,26 @@
|
|
|
1
1
|
# summary
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Show how to deploy a compute app.
|
|
4
4
|
|
|
5
5
|
# description
|
|
6
6
|
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
deploys the app's <name>.compute-meta.xml through the
|
|
11
|
-
Metadata API to trigger the build. The metadata deploy itself returns a job
|
|
12
|
-
ID that can be checked independently with "sf project deploy report
|
|
13
|
-
--job-id <id>". Deploy is asynchronous: this command returns once the build
|
|
14
|
-
has been enqueued, it doesn't wait for the build to finish.
|
|
15
|
-
|
|
16
|
-
Files matching patterns in a .forceignore are excluded from the source
|
|
17
|
-
bundle. Both the compute app's own .forceignore and the one at the project
|
|
18
|
-
root (next to sfdx-project.json) are applied, if present. api-spec.yaml and
|
|
19
|
-
project.toml are always included, since the build can't succeed without them.
|
|
20
|
-
|
|
21
|
-
# flags.source-dir.summary
|
|
22
|
-
|
|
23
|
-
Directory containing the compute app to deploy. Defaults to the current directory.
|
|
7
|
+
This command no longer deploys compute apps. Install the Compute variant of
|
|
8
|
+
the deploy-retrieve plugin and use project deploy start from your Salesforce
|
|
9
|
+
DX project instead.
|
|
24
10
|
|
|
25
11
|
# examples
|
|
26
12
|
|
|
27
|
-
-
|
|
28
|
-
|
|
29
|
-
cd force-app/main/default/platformComputeApps/CreditRatingScorer
|
|
30
|
-
|
|
31
|
-
<%= config.bin %> <%= command.id %> --target-org my-org
|
|
32
|
-
|
|
33
|
-
- Deploy a compute app to an org, from anywhere, by pointing --source-dir at it:
|
|
34
|
-
|
|
35
|
-
<%= config.bin %> <%= command.id %> --source-dir force-app/main/default/platformComputeApps/CreditRatingScorer --target-org my-org
|
|
36
|
-
|
|
37
|
-
# error.notAppDir
|
|
38
|
-
|
|
39
|
-
This directory has no %s.compute-meta.xml. Run this command from inside the compute app's own directory (the one "sf compute generate" created).
|
|
40
|
-
|
|
41
|
-
# error.notAppDir.actions
|
|
42
|
-
|
|
43
|
-
- cd into the compute app's directory (e.g. force-app/main/default/platformComputeApps/<AppName>) and run the command again.
|
|
44
|
-
- Run sf compute generate first if the app hasn't been scaffolded yet.
|
|
45
|
-
|
|
46
|
-
# error.noProcfile
|
|
47
|
-
|
|
48
|
-
%s has no Procfile. A compute app needs a Procfile to define how it starts.
|
|
49
|
-
|
|
50
|
-
# error.noProcfile.actions
|
|
51
|
-
|
|
52
|
-
- Add a Procfile to the app directory before deploying.
|
|
53
|
-
|
|
54
|
-
# error.noApiSpec
|
|
55
|
-
|
|
56
|
-
%s has no api-spec.yaml. A compute app needs an OpenAPI spec to describe its external service.
|
|
57
|
-
|
|
58
|
-
# error.noApiSpec.actions
|
|
59
|
-
|
|
60
|
-
- Add an api-spec.yaml to the app directory before deploying.
|
|
61
|
-
|
|
62
|
-
# info.preparing
|
|
63
|
-
|
|
64
|
-
Preparing deployment for %s...
|
|
65
|
-
|
|
66
|
-
# info.packaging
|
|
67
|
-
|
|
68
|
-
packaging source (%s files, %s)... done
|
|
69
|
-
|
|
70
|
-
# info.uploading
|
|
71
|
-
|
|
72
|
-
uploading source... done
|
|
13
|
+
- Install the plugin and deploy a compute app:
|
|
73
14
|
|
|
74
|
-
|
|
15
|
+
<%= config.bin %> plugins install @salesforce/plugin-deploy-retrieve@compute
|
|
75
16
|
|
|
76
|
-
|
|
17
|
+
<%= config.bin %> project deploy start --metadata ComputeApp:my_app --target-org my-org
|
|
77
18
|
|
|
78
|
-
#
|
|
19
|
+
# error.migrate
|
|
79
20
|
|
|
80
|
-
|
|
21
|
+
This command no longer deploys compute apps.
|
|
81
22
|
|
|
82
|
-
#
|
|
23
|
+
# error.migrate.actions
|
|
83
24
|
|
|
84
|
-
|
|
25
|
+
- Run sf plugins install @salesforce/plugin-deploy-retrieve@compute.
|
|
26
|
+
- From your Salesforce DX project, run sf project deploy start --metadata ComputeApp:<app-name> --target-org <org>.
|
|
@@ -7,6 +7,7 @@ Show the full detail of a single compute telemetry drain.
|
|
|
7
7
|
Shows a single OpenTelemetry drain in full: the compute app it belongs to,
|
|
8
8
|
the signals it forwards, and its exporter endpoint, transport, and headers.
|
|
9
9
|
Use sf compute list telemetry-drain to find a drain's ID.
|
|
10
|
+
Header values are redacted in both human-readable and --json output; header keys are preserved.
|
|
10
11
|
|
|
11
12
|
# args.id.summary
|
|
12
13
|
|
|
@@ -13,7 +13,7 @@ Couldn't determine which compute app to use.
|
|
|
13
13
|
|
|
14
14
|
- Pass --name explicitly.
|
|
15
15
|
- Set the COMPUTE_APP_NAME environment variable.
|
|
16
|
-
- cd into the compute app's own directory (the one with its <name>.
|
|
16
|
+
- cd into the compute app's own directory (the one with its <name>.computeApp-meta.xml file) and run the command again.
|
|
17
17
|
|
|
18
18
|
# error.connectApiRequestFailed
|
|
19
19
|
|
|
@@ -39,7 +39,8 @@ No compute app named %s was found in the org. It may not have been deployed yet,
|
|
|
39
39
|
|
|
40
40
|
# error.appNotFoundInOrg.actions
|
|
41
41
|
|
|
42
|
-
-
|
|
42
|
+
- Run sf plugins install @salesforce/plugin-deploy-retrieve@compute.
|
|
43
|
+
- From your Salesforce DX project, run sf project deploy start --metadata ComputeApp:%s --target-org <org>.
|
|
43
44
|
- Check that the app's directory name matches the DeveloperName used when it was deployed.
|
|
44
45
|
|
|
45
46
|
# error.ambiguousName
|
|
@@ -77,6 +78,15 @@ Couldn't read the log stream: %s
|
|
|
77
78
|
- Run the command again; the log session may have expired.
|
|
78
79
|
- If the problem persists, check your network connection to logplex.heroku.com.
|
|
79
80
|
|
|
81
|
+
# error.logFetchTimedOut
|
|
82
|
+
|
|
83
|
+
Timed out waiting for the log output after %s seconds.
|
|
84
|
+
|
|
85
|
+
# error.logFetchTimedOut.actions
|
|
86
|
+
|
|
87
|
+
- Run the command again.
|
|
88
|
+
- To watch the live log instead of a snapshot, use sf compute tail runtime-log.
|
|
89
|
+
|
|
80
90
|
# error.herokuAppNotFound
|
|
81
91
|
|
|
82
92
|
Heroku didn't find an app named %s.
|
|
@@ -130,7 +140,7 @@ Compute app %s doesn't have a Heroku app identifier yet.
|
|
|
130
140
|
# error.herokuAppIdentifierUnavailable.actions
|
|
131
141
|
|
|
132
142
|
- Wait for the app's current build to finish, then run the command again.
|
|
133
|
-
- If the app has never had a successful build,
|
|
143
|
+
- If the app has never had a successful build, deploy it first with project deploy start.
|
|
134
144
|
|
|
135
145
|
# error.configVarNotFound
|
|
136
146
|
|
|
@@ -146,7 +156,7 @@ Couldn't retrieve metadata for compute app %s: %s
|
|
|
146
156
|
|
|
147
157
|
# error.metadataRetrieveFailed.actions
|
|
148
158
|
|
|
149
|
-
- Confirm the app has been deployed to this org (run
|
|
159
|
+
- Confirm the app has been deployed to this org (run project deploy start first).
|
|
150
160
|
- Check that --name matches the DeveloperName used when it was deployed.
|
|
151
161
|
|
|
152
162
|
# error.sourceDownloadFailed
|
|
@@ -156,7 +166,7 @@ Couldn't download the compute app's source: %s
|
|
|
156
166
|
# error.sourceDownloadFailed.actions
|
|
157
167
|
|
|
158
168
|
- Confirm the target org has compute apps enabled and that you have the DeployCompute or ManageCompute permission.
|
|
159
|
-
- Confirm the app has been deployed to this org (run
|
|
169
|
+
- Confirm the app has been deployed to this org (run project deploy start first).
|
|
160
170
|
|
|
161
171
|
# error.sourceBundleMalformed
|
|
162
172
|
|
|
@@ -209,7 +219,7 @@ The telemetry transport "%s" isn't valid. Use one of: %s.
|
|
|
209
219
|
|
|
210
220
|
# error.invalidHeader
|
|
211
221
|
|
|
212
|
-
|
|
222
|
+
A telemetry header isn't valid. Headers must be passed as key=value.
|
|
213
223
|
|
|
214
224
|
# error.invalidHeader.actions
|
|
215
225
|
|
|
@@ -4,7 +4,7 @@ Scaffold a new compute app into your Salesforce DX project.
|
|
|
4
4
|
|
|
5
5
|
# description
|
|
6
6
|
|
|
7
|
-
Creates the app directory under force-app/main/default/
|
|
7
|
+
Creates the app directory under force-app/main/default/computeApps/<name>/ (or
|
|
8
8
|
--output-dir) with a compute metadata file, a Procfile, a project.toml, and
|
|
9
9
|
starter source in the language you choose with --language. No org is
|
|
10
10
|
contacted, but this command does fetch the starter source for the chosen
|
|
@@ -30,7 +30,7 @@ Directory to create the app in.
|
|
|
30
30
|
|
|
31
31
|
# flags.output-dir.description
|
|
32
32
|
|
|
33
|
-
Defaults to force-app/main/default/
|
|
33
|
+
Defaults to force-app/main/default/computeApps. The app itself is created in a
|
|
34
34
|
subdirectory named after --name.
|
|
35
35
|
|
|
36
36
|
# flags.language.summary
|
|
@@ -50,7 +50,7 @@ scaffolds starters for node and python only.
|
|
|
50
50
|
|
|
51
51
|
- Scaffold a Python compute app into a custom directory:
|
|
52
52
|
|
|
53
|
-
<%= config.bin %> <%= command.id %> --name ReceiptOcr --language python --output-dir force-app/main/default/
|
|
53
|
+
<%= config.bin %> <%= command.id %> --name ReceiptOcr --language python --output-dir force-app/main/default/computeApps/scorers
|
|
54
54
|
|
|
55
55
|
# error.appAlreadyExists
|
|
56
56
|
|
|
@@ -11,6 +11,12 @@ build-log for that.
|
|
|
11
11
|
This prints the most recent log lines and exits. To keep the session open and
|
|
12
12
|
stream new lines as they arrive, use compute tail runtime-log.
|
|
13
13
|
|
|
14
|
+
The recent lines come from the Cedar log buffer (about 1500 lines at most), so
|
|
15
|
+
--num can't return more than that. Fir apps keep no log history, so this
|
|
16
|
+
command isn't supported for them; use compute tail runtime-log instead. The
|
|
17
|
+
command stops waiting after 30 seconds and prints whatever log lines it has
|
|
18
|
+
received by then; if none arrived, it fails with a timeout error.
|
|
19
|
+
|
|
14
20
|
This is an org-mediated operation by --name (the app's DeveloperName) -- the
|
|
15
21
|
org creates a log session with Heroku on your behalf and hands back a
|
|
16
22
|
short-lived, pre-authorized URL that the CLI reads from directly. It doesn't
|
|
@@ -27,6 +33,19 @@ directory's app name if that isn't set either.
|
|
|
27
33
|
|
|
28
34
|
Number of recent log lines to print.
|
|
29
35
|
|
|
36
|
+
# error.firNoLogHistory
|
|
37
|
+
|
|
38
|
+
Fir apps keep no log history, so there is no recent log to fetch for %s.
|
|
39
|
+
|
|
40
|
+
# error.firNoLogHistory.actions
|
|
41
|
+
|
|
42
|
+
- Run sf compute tail runtime-log to watch the live log instead.
|
|
43
|
+
- To learn how Fir differs from Cedar, see https://devcenter.heroku.com/articles/generations.
|
|
44
|
+
|
|
45
|
+
# warning.logFetchPartial
|
|
46
|
+
|
|
47
|
+
The log output didn't finish arriving in time, so only the lines received so far are shown.
|
|
48
|
+
|
|
30
49
|
# info.noBuildsFound
|
|
31
50
|
|
|
32
51
|
Compute app %s has no builds yet, so it has no logs.
|
|
@@ -4,10 +4,10 @@ Retrieve a compute app's source and metadata from an org into your local Salesfo
|
|
|
4
4
|
|
|
5
5
|
# description
|
|
6
6
|
|
|
7
|
-
Creates the compute app's directory under force-app/main/default/
|
|
8
|
-
(or --output-dir), retrieves its <name>.
|
|
7
|
+
Creates the compute app's directory under force-app/main/default/computeApps/<name>/
|
|
8
|
+
(or --output-dir), retrieves its <name>.computeApp-meta.xml through the Metadata
|
|
9
9
|
API, then downloads its source code through the Connect API and extracts it
|
|
10
|
-
into that same directory.
|
|
10
|
+
into that same directory. Deploy it with project deploy start.
|
|
11
11
|
|
|
12
12
|
# flags.name.summary
|
|
13
13
|
|
|
@@ -20,7 +20,7 @@ Directory to create the app in.
|
|
|
20
20
|
|
|
21
21
|
# flags.output-dir.description
|
|
22
22
|
|
|
23
|
-
Defaults to force-app/main/default/
|
|
23
|
+
Defaults to force-app/main/default/computeApps. The app itself is created in a
|
|
24
24
|
subdirectory named after --name.
|
|
25
25
|
|
|
26
26
|
# examples
|
|
@@ -32,7 +32,7 @@ Header to send with each export, as key=value.
|
|
|
32
32
|
|
|
33
33
|
Repeat the flag to send more than one header. A header you pass adds
|
|
34
34
|
or overwrites the one with the same name; the drain's other headers are kept. Header values often carry credentials; they are
|
|
35
|
-
never printed to the terminal
|
|
35
|
+
never printed to the terminal or --json output; header keys are preserved with redacted values.
|
|
36
36
|
|
|
37
37
|
# error.nothingToUpdate
|
|
38
38
|
|