Inject files as part of a Context
complete
K
Kunal Jain
Customers have various reasons to want to inject whole files as part of a Context, especially when doing things like inserting SSH keys or K8s config, etc. that are shared across projects and/or managed by central admin. The concept is that we'd add a set of files to a context. Each would allow upload of a file and/or a textarea where one could paste the contents of a file, and each one would also take a path. At run time, when using a Context, the file would be inserted at the path specified. We'd likely want to have a way to inject it at an absolute path or relative to the working directory, as there are scenarios for each. Alternatively, it might make sense to allow overriding the path of injection in config, but that could get messy.
CCI-I-28
Merged in a post:
Add Base64 encoder/uploader in ENV Var settings page | Base64 Decoder ENV Var
K
Kyle T
Inspired by users and this doc: https://circleci.com/docs/1.0/google-auth/
It is often necessary to include small files or other data that for one reason or another can not be added normally (certain characters can cause issues). The solution is to encode the data with Base64 and then decode the data in your config.I would love to see some sort of variant to environment variables that will allow the uploading of files/data that will be Base64 encoded.
"Automated" decoding, would be ideal. Perhaps a prefix for ENV Vars to automatically interpret as the Base64 decoded data
Imagine uploading
secrets.json
to the ENV Var of $SECRET
, then using this in your project as $B64DECODE_SECRET
. Something like this would be ideal.CCI-I-176
Liya Ai
Linking a support article relevant to this idea: https://support.circleci.com/hc/en-us/articles/360003540393-How-to-insert-files-as-environment-variables-with-Base64
V
Vinny Thanh
Somewhat related to: https://ideas.circleci.com/ideas/CCI-I-1058
C
Chris E
This could be a good solution to https://discuss.circleci.com/t/impossible-to-use-a-private-gcr-io-base-image-on-circle-2-0/15965/2
It doesn't look like it's possible to base64 decode the service account key prior to the docker image being pulled, so having circleci do this automatically would allow for storing base64 encoded keys.