Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat(pipeline executions/orca): attribue to explicitly skip the outputs section in Deployment Manifest or Run Job stage #4032

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

feat(pipeline executions/orca): attribue to explicitly skip the outputs section in Deployment Manifest or Run Job stage #4032

wants to merge 2 commits into from

Commits on Dec 22, 2020

  1. Most K8S deployments do not use the outputs in downstream stages. So,… 

    … if it is not used

users can skip the output of the Deployment Manifest and Run Job (Manifest) stage by
specifiying the attribute noOutput set to false in the stage json.

This significantly reduces the execution context being saved in redis/databse or
sent to the browser.
    Nirmalyasen committed Dec 22, 2020
    Configuration menu
    Copy the full SHA
    d33c26a View commit details
    Browse the repository at this point in the history

  2. feat(kubernetes): attribue to explicitly skip the outputs section in … 

    …Deployment Manifest or Run Job stage

Most K8S deployments do not use the outputs in downstream stages. So, if it is not used
users can skip the output of the Deployment Manifest and Run Job (Manifest) stage by
specifiying the attribute noOutput set to false in the stage json.

This significantly reduces the execution context being saved in redis/databse or
sent to the browser.
    Nirmalyasen committed Dec 22, 2020
    Configuration menu
    Copy the full SHA
    0d36ec9 View commit details
    Browse the repository at this point in the history