-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Proposal: raw contents as a new input artifact type #648
Milestone
Comments
We should also be able to do something like:
|
@pnovotnak although this doesn't address issue #646, would this at all help with your json passing problems? |
sandeepbhojwani
pushed a commit
to sandeepbhojwani/argo
that referenced
this issue
Jan 16, 2018
icecoffee531
pushed a commit
to icecoffee531/argo-workflows
that referenced
this issue
Jan 5, 2022
…#648) * feat: Unified gateway deployment image. Closes argoproj#639 * make deployment logic change * update manifests * Dockerfile change
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I would like to introduce a new input artifact type, called
raw
, which would take the literal value from a "contents" sub field and place it in the specified path as a file. Example below:The use case is to be able to take small pieces of data (json, yaml, diff files) and provide some convenience to the user by not having to do things like echo strings into files, worry about shell escaping, etc...
The text was updated successfully, but these errors were encountered: