You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current alias configuration in the codebase only supports basic shortcuts. It doesn't allow for environment variable expansion or parameter passing. This limitation prevents users from utilizing dynamic values through environment variables, impacting tasks like database exports that rely on such configurations.
Problem
Currently, the alias configuration does not expand environment variables. For instance, when trying to use an environment variable for a database export:
The $DB_USER variable is not being expanded because the code does not handle environment variable substitution. This makes it impossible to use dynamic values set in the environment for the alias commands.
Use Case
Consider a scenario where the user wants to use an alias to run a database export using a user defined by the environment variable DB_USER. The current alias setup doesn't expand $DB_USER, leading to the command not functioning as intended.
Current Code
The existing code in Kamal::Cli::Alias::Command looks like this:
This implementation does not expand environment variables, leading to the inability to pass dynamic values via the environment.
Proposed Fix
To handle environment variable substitution, the code can be modified to expand any environment variables found in the alias command before executing it:
classKamal::Cli::Alias::Command < Thor::DynamicCommanddefrun(instance,args=[])if(_alias=KAMAL.config.aliases[name])# Expand environment variables in the commandexpanded_command=_alias.command.gsub(/\$([a-zA-Z_][a-zA-Z0-9_]*)|\$\{([a-zA-Z_][a-zA-Z0-9_]*)\}/)doENV[$1 || $2]endKamal::Cli::Main.start(Shellwords.split(expanded_command) + ARGV[1..-1])elsesuperendendend
Explanation of the Fix
Environment Variable Expansion:
The proposed change introduces a regular expression that searches for environment variables in two formats: $VAR_NAME and ${VAR_NAME}.
It uses ENV[$1 || $2] to retrieve the value from the environment, ensuring that any specified variables are substituted with their actual values.
Benefits of the Fix
This change will allow users to:
Use environment variables directly in alias commands.
Pass dynamic values to commands, making the system more flexible.
Utilize parameters set in the environment without hardcoding them into the alias configuration.
Current work around
use the entire command as it is to export
use it in makefile
db.export:
kamal accessory exec --quiet --interactive --reuse db "pg_dumpall -U $(DB_USER)" > $(DB_NAME).sql
The text was updated successfully, but these errors were encountered:
Issue Summary
The current alias configuration in the codebase only supports basic shortcuts. It doesn't allow for environment variable expansion or parameter passing. This limitation prevents users from utilizing dynamic values through environment variables, impacting tasks like database exports that rely on such configurations.
Problem
Currently, the alias configuration does not expand environment variables. For instance, when trying to use an environment variable for a database export:
The
$DB_USER
variable is not being expanded because the code does not handle environment variable substitution. This makes it impossible to use dynamic values set in the environment for the alias commands.Use Case
Consider a scenario where the user wants to use an alias to run a database export using a user defined by the environment variable
DB_USER
. The current alias setup doesn't expand$DB_USER
, leading to the command not functioning as intended.Current Code
The existing code in
Kamal::Cli::Alias::Command
looks like this:This implementation does not expand environment variables, leading to the inability to pass dynamic values via the environment.
Proposed Fix
To handle environment variable substitution, the code can be modified to expand any environment variables found in the alias command before executing it:
Explanation of the Fix
$VAR_NAME
and${VAR_NAME}
.ENV[$1 || $2]
to retrieve the value from the environment, ensuring that any specified variables are substituted with their actual values.Benefits of the Fix
Current work around
db.export: kamal accessory exec --quiet --interactive --reuse db "pg_dumpall -U $(DB_USER)" > $(DB_NAME).sql
The text was updated successfully, but these errors were encountered: