Implement detection of oversize SCP's before the build and deployment steps.

[Skripd]

trafficstars

Is your feature request related to a problem? Please describe. The customizations pipeline takes a long time to deploy in our organization. We have many SCP's. If an SCP exceeds 5120 bytes only then, late within the deployment, do we get notified of this problem.

Describe the feature you'd like My team came up with two ideas to mitigate this.

The first one is an automatic minimization of the SCP json files. This reduces SCP size. Deploying a SCP using the web console has this behavior.

Second can we be notified of SCP's that will fail the deployment due to it being larger than 5120 bytes, before the build and deploy steps. For example, an extra pipeline step which does a minimization/sanity check for size. This check could auto complete if no issues were found but require manual approval if a problem related to size is found. Therefore, blocking the deployment.

Additional context No context.

[snebhu3]

@Skripd Thank you for the feature request. I have created an internal backlog to track this request.