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

Extend options to support passthrough #1054

Open
emmjohnson opened this issue Oct 6, 2022 · 1 comment
Open

Extend options to support passthrough #1054

emmjohnson opened this issue Oct 6, 2022 · 1 comment
Assignees
Milestone

Comments

@emmjohnson
Copy link
Contributor

emmjohnson commented Oct 6, 2022

Description of problem

Today, if a workload does not match any of the options, we explode. We are suggesting that it is possible that a workload purposely does not want to match any of the options and would instead like the ability to move on to the next step.

Proposed solution

https://gist.github.com/squeedee/ed833b036ecc8f983d5aaf5801cc5fa8

@emmjohnson emmjohnson moved this to Todo in Cartographer OSS Oct 6, 2022
@emmjohnson emmjohnson self-assigned this Oct 6, 2022
@emmjohnson emmjohnson added this to the TAP 1.4 milestone Oct 6, 2022
@emmjohnson emmjohnson moved this from Todo to Doing in Cartographer OSS Oct 6, 2022
@emmjohnson
Copy link
Contributor Author

emmjohnson commented Oct 6, 2022

Do we have any thoughts what the shape of status.resource[x] should be for the "skipped" resource?

Possibly:

    - name: source-tester
      inputs:
        - name: source-provider
       outputs:
        - name: url
          preview: |
           ...
        - name: revision
          preview: |
            ...

Leaving out stampedRef, templateRef, and conditions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Doing
Development

No branches or pull requests

1 participant