6d062ce271
Allow hosts to be tagged so we can have host specific env variables.
We might want host specific env variables for things like datacenter
specific tags or testing GC settings on a specific host.
Right now you either need to set up a separate role, or have the app
be host aware.
Now you can define tag env variables and assign those to hosts.
For example:
```
servers:
- 1.1.1.1
- 1.1.1.2: tag1
- 1.1.1.2: tag2
- 1.1.1.3: [ tag1, tag2 ]
env_tags:
tag1:
ENV1: value1
tag2:
ENV2: value2
```
The tag env supports the full env format, allowing you to set secret and
clear values.
30 lines
858 B
Ruby
30 lines
858 B
Ruby
module Kamal::Commands::App::Execution
|
|
def execute_in_existing_container(*command, interactive: false, env:)
|
|
docker :exec,
|
|
("-it" if interactive),
|
|
*argumentize("--env", env),
|
|
container_name,
|
|
*command
|
|
end
|
|
|
|
def execute_in_new_container(*command, interactive: false, env:)
|
|
docker :run,
|
|
("-it" if interactive),
|
|
"--rm",
|
|
*role&.env_args(host),
|
|
*argumentize("--env", env),
|
|
*config.volume_args,
|
|
*role&.option_args,
|
|
config.absolute_image,
|
|
*command
|
|
end
|
|
|
|
def execute_in_existing_container_over_ssh(*command, env:)
|
|
run_over_ssh execute_in_existing_container(*command, interactive: true, env: env), host: host
|
|
end
|
|
|
|
def execute_in_new_container_over_ssh(*command, env:)
|
|
run_over_ssh execute_in_new_container(*command, interactive: true, env: env), host: host
|
|
end
|
|
end
|