qetza/replacetokens

CLI to replace tokens in text files with values from the command-line, files or environment variables.

replacetokens's Issues

Allow file path matching to be case insensitive

Add a parameter --case-insensitive-paths so that file matching for all paths (sources, variables...) is case insensitive.

Feature Request: Context-sensitive escaping in docker-compose env files

We are using the replacetokens task to (among other things) replace placeholders in env files for docker compose.
These files have very specific requirements on escaping.
Currently we are using the "Replace Tokens" task, but it does not currently support escaping in these env files.
I realize this is a very specific use-case, but it is not possible to cover it with the custom-escaping config, due to the context-sensitive nature of the escaping.

Do you think it makes sense to add special escaping for *.env files here?

Basically what we need is the bash script below, which works well (up to a few edge cases). A bash script in the pipeline does not have access to all the variables though, afaik.

# Generate sed s-command to replace one literal with another one.
# The key is assumed to contain only characters [A-Z_]
function sub() {
  KEY="$1"
  VALUE=$(printf '%s' "$2" | sed -e 's/[\|&]/\\&/g')
  printf 's|#{%s}#|%s|g' "$KEY" "$VALUE"
}

# - Single quoted values need to have single quotes escaped.
# - Double quoted values need to have double quotes and backslashes escaped.
# - Double- und unquoted values need to have the dollar sign escaped.
VALUE_SQ=$(printf "%s" "$VALUE" | sed -e "s|'|\\\\'|g")
VALUE_DQ=$(printf "%s" "$VALUE" | sed -e 's|\\|\\\\|g' -e 's|"|\\"|g' -e 's|\$|$$|g')
VALUE_UQ=$(printf "%s" "$VALUE" | sed -e 's|\$|$$|g')
sed -i \
  -e '/^[^=]*='\''/ '"$(sub "$KEY" "$VALUE_SQ")" \
  -e '/^[^=]*="/ '"$(sub "$KEY" "$VALUE_DQ")" \
  -e "$(sub "$KEY" "$VALUE_UQ")" \
  "$FILE"

Support comments in JSON

Replacing token with environment variable not working

I have been trying to replace tokens in the file with the help of environment variables. Tokens are replaced with blank values.

As per README, tried using --variables '$VARS' to replace tokens with values from environment variables.

Logs:

Support glob pattern in variable file paths

Add support for glob patterns when referencing a file in variables:

• use fast glob
• multi patterns separated by semi-colon

Variable names should be case insensitive

Most build systems are case insensitive for their variables

• Azure DevOps do comparison on uppercase names
• GitHub forces variable names to uppercase

so the lib should be case insensitive too to avoid issue like qetza/replacetokens-task#8

Allow CLI to access env as variables

To simplify the use of environment variables as variables add a new parameter --use-env to initialize variables with all env variables:

• parameter --variables will be optional if --use-env is specified
• variables specified in --variables will override env variables if they have the same name

#15

Allow to include or exclude dot paths in matching

Add a parameter --include-dot-paths so that file starting with a dot (.) are included in the glob results.

Support YAML variable files