If you want to extend the drone file to include another custom ‘kind’, you can’t quite yet.
For some reason drone doesn’t introspect the ‘kind’ when it parses the file. It will ingest every type of ‘kind’ and assume that is a drone pipeline, and show it in the pipeline runtime.
For instance if you had a drone file:
--- kind: pipeline name: default steps: - name: boston image: boston/docker-stuff --- kind: authorizer name: my-auther spec: - name: this-is-used-by-a-plugin-or-extension
Do we need to add custom parsing or am I doing this wrong? Trying to build an extension that acts like an authorizer but I don’t want to deviate from the drone file.