Commit Graph

15 Commits (89ea52c058029701cecc1f094cb6bae045e5e344)

Author SHA1 Message Date
johndmulhausen 588e30e6af Merge pull request #492 from joonathan/patch-1
Use `echo -n` for less ambiguous base64 secret example
2016-05-31 16:32:03 -07:00
johndmulhausen af55ba8098 Merge pull request #545 from AlginMaduro/patch-1
Updated secrets index.md
2016-05-24 16:23:51 -07:00
Pavel Strashkin 6dd070c5d9 Update index.md
Fixes typo in "Using Secrets as Environment Variables" section
2016-05-21 15:42:15 -07:00
AlginMaduro 05276f34cf Updated index.md
Without -n option to echo. Without the -n the file would contain a newline at the end.
https://scottlinux.com/2012/09/01/encode-or-decode-base64-from-the-command-line/ as reference
2016-05-20 12:15:37 +02:00
Joonathan Mägi 5c9d6060f3 Use `echo -n` for less ambiguous base64 secret example
One could be bitten by having unexpected newline characters in base64 encoded secrets (reference: https://github.com/kubernetes/kubernetes/issues/23404).
Calling `echo -n` will omit the trailing newline character.

`
     The echo utility writes any specified operands, separated by single blank (` ') characters and followed by
     a newline (`\n') character, to the standard output.

     The following option is available:

     -n    Do not print the trailing newline character.  This may also be achieved by appending `\c' to the end
           of the string, as is done by iBCS2 compatible systems.  Note that this option as well as the effect
           of `\c' are implementation-defined in IEEE Std 1003.1-2001 (``POSIX.1'') as amended by Cor. 1-2002.
           Applications aiming for maximum portability are strongly encouraged to use printf(1) to suppress the
           newline character.
`
2016-05-11 14:33:33 +03:00
Jan Chaloupka 66f23d05d3 Remove "a" article in "Once the a secret is fetched, ..." 2016-05-03 12:02:05 +02:00
johndmulhausen 93c5d65ec7 Merge pull request #357 from brianredbeard/b64-cli-errata
docs: Clarify use of the base64 utility
2016-04-13 13:36:25 -07:00
johndmulhausen 56e0556bc4 Merge pull request #319 from rickypai/patch-1
Fix secrets examples to be valid json
2016-04-11 14:12:41 -07:00
Brian 'Redbeard' Harrington e90337bf19 docs: Clarify use of the base64 utility
The base64 utility has different options on both Darwin and Linux.
Adding clarification as to how the use of these utilities differ
on platforms.
2016-04-09 13:38:12 -07:00
Spencer Brown 87628894c7 Update secrets/index.md
fixing example for Consuming Secret Values from Environment Variables
2016-04-08 14:49:03 -05:00
Ricky Pai 404420b05d Fix secrets examples to be valid json
Working through the secrets example, I found some of the json descriptors to be invalid. This fixes them.
2016-04-04 15:14:42 -07:00
johndmulhausen 0d31281f27 Surfaces previously hidden topics that had URL conflicts, moves pages to index.md as often as possible 2016-03-29 14:58:48 -07:00
John Mulhausen f16668b45f 1.2 additions for user-guide/ 2016-03-07 12:09:02 +00:00
John Mulhausen a6f6fd01cd 1.2 additions for getting-started-guides/ and new non-Markdown files for user-guides 2016-03-06 17:55:12 +00:00
John Mulhausen 4c9e72c518 Moving docs from /vX to /docs; we will use branches for old versions. 2016-02-29 15:17:22 -08:00