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.

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

feat(core): Support deserializing Execution.initialConfig #3019

Merged
merged 1 commit into from
Jul 3, 2019

Conversation

ajordens
Copy link
Contributor

@ajordens ajordens commented Jul 2, 2019

Also adds support for using initialConfig.enabled as a short circuit
of the EnabledPipelineValidator check.

This seems reasonable as a user can already submit pipeline json against
an arbitrary pipeline config id (that may or may not exist).

Providing an ability to explicitly override the enabled check seems
harmless.

@ajordens ajordens requested a review from robzienert July 2, 2019 20:51
@robzienert
Copy link
Member

Oh, huh. That's what initialConfig is for?

Also adds support for using `initialConfig.enabled` as a short circuit
of the `EnabledPipelineValidator` check.

This seems reasonable as a user can already submit pipeline json against
an arbitrary pipeline config id (that may or may not exist).

Providing an ability to explicitly override the enabled check seems
harmless.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants