Flag to have wait update in intervals rather than continuous

[divinedragon]

Currently, sf project deploy or sf project retrieve does a continuous Elapsed counter. We deploy to our Salesforce org via our CDP pipeline, and this continuous counter creates the log file of ~15MB for validation and deployment for the full codebase.

-> sf project deploy start -m "CustomObject:MessagingSession"
 ›   Warning: @salesforce/cli update available from 2.83.7 to 2.84.6.

 ─────────────── Deploying Metadata ───────────────

 Deploying v63.0 metadata to <> using the v63.0 SOAP API.

 ✔ Preparing 95ms
 ◯ Waiting for the org to respond - Skipped
 ✔ Deploying Metadata 3.05s
   ▸ Components: 20/20 (100%)
 ◯ Running Tests - Skipped
 ◯ Updating Source Tracking - Skipped
 ✔ Done 0ms

 Status: Succeeded
 Deploy ID: 
 Target Org: 
 Elapsed Time: 3.14s

A flag (example --wait-interval 15) should wait and query for the latest update with the interval duration.

[cristiand391]

the polling frequency for deploy/retrieves is not customizable by the user (it's calculated by us depending on the amount of components in the operation).

We deploy to our Salesforce org via our CDP pipeline, and this continuous counter creates the log file of ~15MB

that sounds like you are getting the non-CI, animated status update printed out. If you are in a CI env, we print a machine-friendly version that you can customize the frequency via the SF_CI_UPDATE_FREQUENCY_MS and SF_CI_HEARTBEAT_FREQUENCY_MS env vars, see:
https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_env_variables.htm#sfdx_dev_cli_env_variables

suggestion:
If that CDP pipeline is not CI/isn't detected as one, set CI=true to trigger the CI output:
https://github.com/oclif/multi-stage-output/blob/b82b18e897f1850fb7265dc6e37fefa95469f924/src/multi-stage-output.tsx#L23C1-L44C2

example in the after video of the non-animated CI output (see there's no colors)
salesforcecli/plugin-deploy-retrieve#1215

[divinedragon]

Hey, thanks for the pointer to the documentation. I was able to get the intended behaviour by setting the CONTINUOUS_INTEGRATION=true in my pipeline configuration file. CI=true is short and can be easily missed.

[cristiand391]

cool.
fwiw, we have a ticket for making the library also print CI output when running inside a TTY context but for now setting CI=true is the workaround.