-
Notifications
You must be signed in to change notification settings - Fork 75
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
Teach pipeline validator about terminate processor #847
Conversation
a493f90
to
bb47636
Compare
- description: Add `terminate` processor to list pipeline spec. | ||
type: enhancement | ||
link: https://github.com/elastic/package-spec/pull/847 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this could be added in a 3.3.2. Both spec 3.3 and the terminate processor were introduced in 8.16,
- description: Add `terminate` processor to list pipeline spec. | |
type: enhancement | |
link: https://github.com/elastic/package-spec/pull/847 | |
- version: 3.3.2-next | |
changes: | |
- description: Add `terminate` processor to list pipeline spec. | |
type: enhancement | |
link: https://github.com/elastic/package-spec/pull/847 |
@@ -48,6 +48,7 @@ spec: | |||
# set_security_user: false # Applicable to packages? | |||
sort: { type: object } | |||
split: { type: object } | |||
terminate: { type: object } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Btw, please add a patch below, so this processor is actually not available in older versions of the spec, something like this:
- before: 3.3.0
patch:
- op: remove
path: /definitions/processors/terminate # remove terminate processor validation
03f60e1
to
d304004
Compare
💔 Build Failed
Failed CI Steps
History
cc @efd6 |
@jsoriano It seems that that does not work, unless I have misunderstood your instructions. |
- before: 3.3.0 | ||
patch: | ||
- op: remove | ||
path: /definitions/processors/terminate # remove terminate processor validation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This array item should be added as the first one (as it references a newer version in the before
field).
And looking at the error:
failed to load schema for "integration/elasticsearch/pipeline.spec.yml": failed to apply patch: error in remove for path: '/definitions/processors/terminate': unable to remove nonexistent key: terminate: missing value
the path should be updated too.
I think it should be like this:
versions:
- before: 3.3.0
patch:
- op: remove
path: /definitions/processor/properties/terminate # remove terminate processor validation
- before: 3.1.0
patch:
- op: remove
path: /definitions/processors/if # remove rename processor validation
- op: remove
path: /definitions/processors/then # remove rename processor validation
Continuing with this change in #857. |
What does this PR do?
Add terminate processor to list of valid processors.
Why is it important?
Currently the processor cannot be used.
Checklist
test/packages
that prove my change is effective.spec/changelog.yml
.Related issues