You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 27, 2020. It is now read-only.
What happened: Having a hard time specifying JSON on the command line. And I don't wish to read from a file in git/etc in every case. Need a clean way to code stdin for kubectl into the job.
What you expected to happen: A stdin param would make this easy.
How to reproduce it (as minimally and precisely as possible): Try bash here docs or bash here strings with apply operations that idempotently create namespaces. Quoting and carriage returns make these hacks untenable.
Anything else we need to know?: I generate my pipelines from jsonnet. It renders to json/yaml all the same.
Environment: docker-compose file from main repo.
Here's a concept sketch of what I'm looking for. Perhaps there is already something like this that I missed.
@superbrothers Is that method idempotent or convergent? Trying to create the namespace more than once using that kubectl syntax would usually throw a non-zero error code, in my experience. Yes, other use cases exist but I'll try sorting through it in the current framework until I can state them concretely.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a BUG REPORT or FEATURE REQUEST?:
What happened: Having a hard time specifying JSON on the command line. And I don't wish to read from a file in git/etc in every case. Need a clean way to code stdin for kubectl into the job.
What you expected to happen: A
stdin
param would make this easy.How to reproduce it (as minimally and precisely as possible): Try bash here docs or bash here strings with
apply
operations that idempotently create namespaces. Quoting and carriage returns make these hacks untenable.Anything else we need to know?: I generate my pipelines from jsonnet. It renders to json/yaml all the same.
Environment: docker-compose file from main repo.
Here's a concept sketch of what I'm looking for. Perhaps there is already something like this that I missed.
The text was updated successfully, but these errors were encountered: