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
This is more of a question. Looking through the docs, I'm not sure if it's possible to split the docker host (DOCKER_HOST) configuration in Pulumi.yml:
name: pulumi_dockerruntime:
name: pythonoptions:
toolchain: poetryvirtualenv: .venvtypechecker: mypydescription: Use the docker provider to setup local and remote containersconfig:
docker:host:
value: unix:///var/run/docker.sockdocker:host:
value: ssh://user@remote-host:22docker:sshOpts:
value:
- -o
- StrictHostKeyChecking=no
- -o
- UserKnownHostsFile=/dev/nullpulumi:tags:
value:
pulumi:template: https://www.pulumi.com/ai/api/project/52d80566-92ad-49af-8b0c-0e5eb4f3d53e.zip
This of course fails as it's a duplicate key
λ pulumi config
error: could not unmarshal '/Users/lance.stephens/git/pulumi_docker/Pulumi.yml': yaml: unmarshal errors:
line 12: mapping key "docker:host" already defined at line 10
My use case is that I want some containers to be local while others are remote (or both). An example of this workflow is that on the pulumi host (controller?), it needs prometheus, grafana, and the node-exporter for linux. But on remote nodes, certain prometheus exporters will be deployed (e.g., mongo, redis, elasticsearch, etc.)
The business logic can easily handle this, but not sure how pulumi abstracts the underlying terraform and if that's possible without writing separate stacks.
The text was updated successfully, but these errors were encountered:
This is more of a question. Looking through the docs, I'm not sure if it's possible to split the docker host (DOCKER_HOST) configuration in
Pulumi.yml
:This of course fails as it's a duplicate key
My use case is that I want some containers to be local while others are remote (or both). An example of this workflow is that on the pulumi host (controller?), it needs prometheus, grafana, and the node-exporter for linux. But on remote nodes, certain prometheus exporters will be deployed (e.g., mongo, redis, elasticsearch, etc.)
The business logic can easily handle this, but not sure how pulumi abstracts the underlying terraform and if that's possible without writing separate stacks.
The text was updated successfully, but these errors were encountered: