Sep 25, 2024 · For secrets that are not in base64, such as PEM files, you can convert and encode them in base64, and then store them as Harness file secrets before decoding them in …

Nov 12, 2025 · When enabled, all secrets fetched from external secret managers such as Vault must be provided in Base64 format. This ensures consistent handling and compatibility across …

Nov 20, 2025 · For the purposes of the example, we’re just echo-ing the output, but you could generate the base64 in a number of ways, such as piping helm to base64: ```helm template | …

2 days ago · <+configFile.getAsBase64("CONFIG_FILE_ID")>: Get config file contents with Base64-encoding. For more information, go to Use config files in your deployments. Stage …

Feb 13, 2024 · Use Base64 to avoid new lines If you are going to use a config file in a manifest or shell script, be aware that <+configFile.getAsString()> can cause problems by adding new …

May 14, 2025 · Save the base64-encoded file as a Harness file secret. In your pipeline, in the step where you need to use the GCP secret, decode the file secret and write it to a .json file.

Oct 28, 2025 · If you choose to base64 encode them, use the data field instead of stringData. Both methods will convert the secrets into base64-encoded format on the server. Create a …

Oct 13, 2025 · If you're creating a Kubernetes secrets and it's not base64 encoded, then you can use stringData instead. For more information, go to Constraints on Secret names and data.

Oct 9, 2025 · To achieve this, you can use an expression to output the YAML pipeline in base64-encoded form, e.g., through a previous stage or step that outputs the pipeline YAML in base64 …

Copy the value of lookerMasterKey from the secret looker-secrets and decode it using the following command or any base64 decoder. You’ll need to decode it twice.