@revoengine/cli 1.0.27 → 1.0.28

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/README.md CHANGED
@@ -444,7 +444,7 @@ revo schedules push --all --yes --force
444
444
 
445
445
  `--force` permits adopting a missing Schedule baseline or overwriting reviewed target drift. It also approves a reviewed transition between Job Template and Materialized View targets under one Schedule Stable Key. Materialized View refresh Schedules are included with the other Schedules and identify their Database View by Stable Key and refresh mode, never by a source UUID. User-managed `JOB_TEMPLATE` and `PLATFORM_OPERATION` schedules of kind `refresh_materialized_view` are supported. Other platform operations, `AGENT`, and system-managed Schedules are excluded; `--strict` treats exclusions as incomplete coverage.
446
446
 
447
- Pull initializes each Schedule's editable activation candidate from the source. A new target Schedule is created inactive, while a configuration update preserves its target activation state. `activationCandidate` records the desired active state. Plans report activation-only differences as `activation-drift`, including without a target lock baseline; repository plans mark them as pending changes, and strict plans or deployment verification do not report convergence until they are aligned. `schedules push --all --yes --activate` aligns verified new, updated and otherwise unchanged Schedules with manifest activation intent, including disabling them. Failed configuration preflight skips activation; changed definitions or dependencies block activation. Interactive activation asks for a second confirmation. Repository `deploy` and named `migrate` leave this activation step to the dedicated command.
447
+ Pull initializes each Schedule's editable activation candidate from the source. A new target Schedule is created inactive, while a configuration update preserves its target activation state. `activationCandidate` records the desired active state. Plans report activation-only differences as `activation-drift`, including without a target lock baseline. Repository `plan/deploy` without `--activate` verifies definition convergence and preserves target activation; activation-only drift remains informational and does not fail a strict plan or final verification. With `--activate`, activation differences require changes and are aligned only after verified writes and pruning. Plan and deploy must use the same activation policy. `schedules push --all --yes --activate` also aligns verified new, updated and otherwise unchanged Schedules, including disabling them. Failed configuration preflight skips activation; changed definitions or dependencies block activation. Interactive activation asks for a second confirmation. Named `migrate` retains its separate activation-convergence checks.
448
448
 
449
449
  Use `--project` to select a saved project explicitly (`--env` remains a compatible alias):
450
450
 
@@ -508,7 +508,7 @@ Resource plans support `--json` for automation and generally support `--strict`
508
508
  - `--force` approves only explicitly supported risky or drifted operations; it is not a universal bypass.
509
509
  - Writes resolve the target UUID and version immediately before mutation and verify the portable result afterward.
510
510
  - Stable Keys cross environments; source UUIDs, versions, members, users, ACLs, and other target-local identities do not.
511
- - New Schedules and Events are created inactive; ordinary updates preserve target activation. Dedicated `schedules push --all --yes --activate` aligns manifest activation intent for verified new, updated and otherwise unchanged Schedules, including disabling them. Activation drift is shown by plans and prevents repository strict-plan/deployment convergence until aligned. `events push --all --yes --activate` aligns verified Events with manifest activation intent, including disabling them; configuration failures skip Event activation. Interactive activation requires an additional confirmation. `deploy` and `migrate` do not run this activation phase.
511
+ - New Schedules and Events are created inactive; ordinary updates preserve target activation. Dedicated `schedules push --all --yes --activate` aligns manifest activation intent for verified new, updated and otherwise unchanged Schedules, including disabling them. Activation drift is shown by plans and affects repository convergence only with --activate. `events push --all --yes --activate` aligns verified Events with manifest activation intent, including disabling them; configuration failures skip Event activation. Interactive activation requires an additional confirmation. `deploy --activate` runs this phase after verified writes and pruning; named `migrate` leaves activation to dedicated commands.
512
512
  - Groups and Role Groups are intentionally late phases because they can affect ownership and access.
513
513
  - Lock data is stored in `.revoengine/revo.lock.json`; API tokens are never persisted in the project.
514
514
 
@@ -643,7 +643,7 @@ Portable comparison includes ordinary Component metadata and full structured Dat
643
643
 
644
644
  Endpoint and Job Template pins use the API content identity `v1:sha256:<64 lowercase hex characters>`, independently of the configuration hash. Latest bindings explicitly clear old digest pins. Endpoint `pinnedDigest` fingerprints from older CLI versions are upgraded in memory only when their exact local Component source proves the content identity; otherwise re-pull the source definition. Numeric-only Job Template pins remain explicitly unsupported; use a canonical digest pin instead.
645
645
 
646
- Schedule and Event activation differences remain pending changes even if their configuration matches. Ordinary deployment preserves activation; use the existing explicit `schedules push --all --yes --activate` or `events push --all --yes --activate` step to align it. Strict plans and final verification cannot report convergence until activation matches. Deprecated Schedule `targetVersion` is reported diagnostically; the backend does not use it to select a Job Template revision.
646
+ Repository `plan/deploy` without `--activate` preserves existing Event and Schedule activation and creates new definitions inactive. Differences from manifest activation remain visible as `activation-drift`, but do not prevent definition convergence. With `--activate`, strict plans and final verification require activation to match the manifest. Reviewed deployment still fences live target activation and rejects changes after planning, in either mode. Named migration and dedicated family plans retain their activation-convergence checks. Deprecated Schedule `targetVersion` is reported diagnostically; the backend does not use it to select a Job Template revision.
647
647
 
648
648
  `CUSTOM_NODEJS` deployment verifies runtime availability and the active desired revision after source readback. Automatic deployment waits up to two minutes for readiness; failed attempts, manual activation requirements and unavailable/pending revisions fail verification without adopting a deployment baseline. Re-run after the runtime is ready. Named `env diff/apply` also reports unavailable unchanged custom runtimes and returns an error on unverified writes. Definition synchronization does not invoke provider/plugin tests; component dependencies and their pinned revisions are checked with read-only API calls, including unchanged definitions.
649
649
 
package/dist/src/cli.js CHANGED
@@ -198,7 +198,7 @@ async function runMain(args, argv) {
198
198
  const command = args._[0];
199
199
  const noPositionals = args._.length === 0;
200
200
  if (command === 'version' || ((args.version !== undefined || args.V !== undefined) && noPositionals)) {
201
- print(args.json ? { version: packageVersion, capabilities: { workspacePrune: true, reviewedPrunePlan: true, reviewedDeploymentPlan: true, componentMutationReview: true, reviewedAutomationActivation: true } } : packageVersion);
201
+ print(args.json ? { version: packageVersion, capabilities: { workspacePrune: true, reviewedPrunePlan: true, reviewedDeploymentPlan: true, componentMutationReview: true, reviewedAutomationActivation: true, preservedAutomationActivation: true } } : packageVersion);
202
202
  return;
203
203
  }
204
204
  if (command === 'info' || ((args.i === true || args.info === true) && noPositionals)) {
@@ -128,6 +128,8 @@ function printMigrationPlan(context, plan) {
128
128
  context.println(`Diagnostics: ${plan.warnings.length} warning(s), ${plan.blockers.length} blocker(s).`);
129
129
  if (plan.policy.activateAutomations)
130
130
  context.println('Automation activation: align tracked Events and Schedules with repository active values after verified writes and pruning.');
131
+ else if (plan.from === 'workspace')
132
+ context.println('Automation activation: preserve target Event and Schedule active values; create new definitions inactive.');
131
133
  if (plan.sourcePull.mode === 'repository') {
132
134
  context.println('Source snapshot: repository workspace (no remote source pull).');
133
135
  }
@@ -253,7 +253,7 @@ function summarizeEndpointPhase(plan) {
253
253
  blockers,
254
254
  };
255
255
  }
256
- function summarizeSchedulePhase(plan) {
256
+ function summarizeSchedulePhase(plan, alignActivation = true) {
257
257
  const operations = emptyOperations();
258
258
  for (const item of plan.items) {
259
259
  operations[migrationItemOperation(item, scheduleItemAction(item))] += 1;
@@ -272,7 +272,7 @@ function summarizeSchedulePhase(plan) {
272
272
  return {
273
273
  order: 6,
274
274
  resource: 'schedule',
275
- needsChanges: operations.create + operations.update > 0 || plan.items.some((item) => item.status === 'activation-drift'),
275
+ needsChanges: operations.create + operations.update > 0 || (alignActivation && plan.items.some((item) => item.status === 'activation-drift')),
276
276
  readyToMigrate: blockers.length === 0,
277
277
  verdict: phaseVerdict(blockers, warnings),
278
278
  operations,
@@ -280,7 +280,7 @@ function summarizeSchedulePhase(plan) {
280
280
  blockers,
281
281
  };
282
282
  }
283
- function summarizeEventPhase(plan) {
283
+ function summarizeEventPhase(plan, alignActivation = true) {
284
284
  const operations = emptyOperations();
285
285
  for (const item of plan.items) {
286
286
  operations[migrationItemOperation(item, eventItemAction(item))] += 1;
@@ -296,13 +296,15 @@ function summarizeEventPhase(plan) {
296
296
  .map((item) => `Event "${item.stableKey || item.name}" has no target lock baseline; source-wins migration will align or adopt it.`),
297
297
  ...plan.items
298
298
  .filter((item) => item.status === 'activation-drift')
299
- .map((item) => `Event "${item.stableKey || item.name}" has activation drift; activation requires repository plan/deploy --activate or the dedicated events push --activate step.`),
299
+ .map((item) => alignActivation
300
+ ? `Event "${item.stableKey || item.name}" has activation drift; activation requires repository plan/deploy --activate or the dedicated events push --activate step.`
301
+ : `Event "${item.stableKey || item.name}" has activation drift; repository deployment preserves target activation without --activate.`),
300
302
  ])];
301
303
  const blockers = [...new Set(plan.blockers)];
302
304
  return {
303
305
  order: 7,
304
306
  resource: 'event',
305
- needsChanges: operations.create + operations.update > 0 || plan.items.some(item => item.status === 'activation-drift'),
307
+ needsChanges: operations.create + operations.update > 0 || (alignActivation && plan.items.some(item => item.status === 'activation-drift')),
306
308
  readyToMigrate: blockers.length === 0,
307
309
  verdict: phaseVerdict(blockers, warnings),
308
310
  operations,
@@ -616,8 +618,8 @@ function combinePlan(input) {
616
618
  ...(input.agents ? [summarizeAgentPhase(input.agents)] : []),
617
619
  ...(input.jobTemplates ? [summarizeJobTemplatePhase(input.jobTemplates)] : []),
618
620
  ...(input.endpoints ? [summarizeEndpointPhase(input.endpoints)] : []),
619
- ...(input.schedules ? [summarizeSchedulePhase(input.schedules)] : []),
620
- ...(input.events ? [summarizeEventPhase(input.events)] : []),
621
+ ...(input.schedules ? [summarizeSchedulePhase(input.schedules, input.migrationInput.sourceMode !== 'workspace' || input.migrationInput.activateAutomations === true)] : []),
622
+ ...(input.events ? [summarizeEventPhase(input.events, input.migrationInput.sourceMode !== 'workspace' || input.migrationInput.activateAutomations === true)] : []),
621
623
  ...(input.groups ? [summarizeGroupPhase(input.groups)] : []),
622
624
  ...(input.roleGroups ? [summarizeRoleGroupPhase(input.roleGroups)] : []),
623
625
  ].map((phase) => ({ ...phase, order: RESOURCE_ORDER.indexOf(phase.resource) + 1 })).map((phase) => applyWorkspaceDeploymentPolicy(input.migrationInput, phase, input))
@@ -1555,7 +1557,7 @@ export async function runMigration(input) {
1555
1557
  envName: environmentKey,
1556
1558
  stableKeyName,
1557
1559
  }), input.onProgress);
1558
- const liveSchedulePhase = applyWorkspaceDeploymentPolicy(input, summarizeSchedulePhase(liveSchedulePlan), {
1560
+ const liveSchedulePhase = applyWorkspaceDeploymentPolicy(input, summarizeSchedulePhase(liveSchedulePlan, input.sourceMode !== 'workspace' || input.activateAutomations === true), {
1559
1561
  schedules: liveSchedulePlan,
1560
1562
  });
1561
1563
  if (!liveSchedulePhase.readyToMigrate) {
@@ -1592,7 +1594,7 @@ export async function runMigration(input) {
1592
1594
  envName: environmentKey,
1593
1595
  stableKeyName,
1594
1596
  }), input.onProgress);
1595
- const liveEventPhase = summarizeEventPhase(liveEventPlan);
1597
+ const liveEventPhase = summarizeEventPhase(liveEventPlan, input.sourceMode !== 'workspace' || input.activateAutomations === true);
1596
1598
  if (!liveEventPhase.readyToMigrate) {
1597
1599
  const verification = await planWorkspace({
1598
1600
  ...input,
package/dist/src/ui.js CHANGED
@@ -179,9 +179,9 @@ function renderCommandCatalog() {
179
179
  commandRow('revo metadata apply [--project <name>] --yes [--skip-partitions]', 'Populate missing stable-key metadata'),
180
180
  commandRow('revo pull --all|--resources <list> --yes [--skip-groups] [--force] [--json]', 'Build the repository workspace from the configured runtime source'),
181
181
  commandRow('revo diff [--json]', 'Show only workspace-to-target resource differences without writes'),
182
- commandRow('revo plan [--activate] [--prune] [--out file] [--force] [--strict] [--json] [--hints]', 'Plan tracked workspace upserts and optional Stable Key deletions without writes'),
182
+ commandRow('revo plan [--activate] [--prune] [--out file] [--force] [--strict] [--json] [--hints]', 'Plan tracked definitions; preserve automation activation unless --activate'),
183
183
  commandRow('revo plan update [--json]', 'Update the local Stable Key source digest index without contacting the target'),
184
- commandRow('revo deploy [--yes] [--activate] [--prune] [--reviewed-plan file] [--force] [--json]', 'Review, confirm, deploy and prune tracked resources in dependency order'),
184
+ commandRow('revo deploy [--yes] [--activate] [--prune] [--reviewed-plan file] [--force] [--json]', 'Deploy tracked definitions; preserve automation activation unless --activate'),
185
185
  commandRow('revo migrate plan --from <env> --to <env> [--resources <list>] [--skip-groups] [--force] [--json] [--hints]', 'Preview twelve resource families and identity dependencies'),
186
186
  commandRow('revo migrate run --from <env> --to <env> [--resources <list>] [--skip-groups] --yes [--force] [--json]', 'Pull, plan, migrate, and verify resources in dependency order'),
187
187
  commandRow('revo migrate verify --from <env> --to <env> [--resources <list>] [--json]', 'Verify target resources against a fresh temporary source pull'),
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@revoengine/cli",
3
- "version": "1.0.27",
3
+ "version": "1.0.28",
4
4
  "description": "CLI package for the RevoEngine Platform API",
5
5
  "type": "module",
6
6
  "main": "dist/src/index.js",