Differences

This shows you the differences between two versions of the page.

--- shell_or_bash_scripts [2017/05/28 11:48] – skipidar
+++ shell_or_bash_scripts [2022/10/14 06:01] (current) – [Double-Dash in Shell commands] skipidar
@@ Line 10: / Line 10: @@
 |https://www.shellcheck.net/|Check the syntax of the shell live|
-|http://www.artificialworlds.net/blog/2012/10/17/bash-associative-array-examples/|
+|http://www.artificialworlds.net/blog/2012/10/17/bash-associative-array-examples/| |
-|https://linuxconfig.org/bash-scripting-tutorial|
+|https://linuxconfig.org/bash-scripting-tutorial| |
-|http://www.tldp.org/LDP/Bash-Beginners-Guide/html/Bash-Beginners-Guide.html#chap_11|
+|http://www.tldp.org/LDP/Bash-Beginners-Guide/html/Bash-Beginners-Guide.html#chap_11| |
-|http://tldp.org/HOWTO/Bash-Prog-Intro-HOWTO.html|
+|http://tldp.org/HOWTO/Bash-Prog-Intro-HOWTO.html| |
 ===== Executing or Sourcing the script=====
@@ Line 120: / Line 120: @@
+==== Input from command line ====
+If a command expects **a file** as input - one can pass input from STDOUT instead,
+without storing the output to a file first by using following syntax
+**oc create -f** expects a file here.
+<code>
+oc process -f build/my-build-template.yaml  GITSERVER=$GITSERVER | oc create -f -
+oc process -f build/my-build-template.yaml  GITSERVER=$GITSERVER | oc create -f /dev/stdin
+</code>
+==== Double-Dash -- in Shell commands ====
+A double-dash in a shell command signals the end of options and disables further option processing.
+https://www.baeldung.com/linux/double-dash-in-shell-commands
+<sxh shell>
+# If we use the same approach, we'll receive an error:
+# That's because grep treats "--hello" as a multi-character command option.
+grep "--hello" data.txt
+#works
+grep -- --hello data.txt
+</sxh>