fancy-eve-82724
07/04/2024, 2:44 PMpulumi preview
will timeout because the docker Provider is assuming it can access the target host.dry-keyboard-94795
07/04/2024, 2:53 PMdry-keyboard-94795
07/04/2024, 2:54 PMfancy-eve-82724
07/04/2024, 2:54 PMfancy-eve-82724
07/04/2024, 2:55 PMadventurous-butcher-54166
07/04/2024, 2:55 PMfancy-eve-82724
07/04/2024, 2:56 PMadmin_docker = docker.Provider(
"docker-admin",
host=admin_server.public_ip.apply(
lambda l: f"<ssh://ec2-user>@{l}"
),
opts=pulumi.ResourceOptions(
parent=admin_server,
depends_on=[admin_server]
)
)
dry-keyboard-94795
07/04/2024, 2:57 PMadmin_server
is an ec2 resource?fancy-eve-82724
07/04/2024, 2:57 PMadmin_server = aws.ec2.Instance(...)
adventurous-butcher-54166
07/04/2024, 2:59 PMfancy-eve-82724
07/04/2024, 3:00 PMpulumi_docker 4.5.4
dry-keyboard-94795
07/04/2024, 3:00 PMdry-keyboard-94795
07/04/2024, 3:02 PMfancy-eve-82724
07/04/2024, 3:02 PMfancy-eve-82724
07/04/2024, 3:02 PMadventurous-butcher-54166
07/04/2024, 3:02 PMdepends_on
- that is is the Docker provider created before the ec2 creation?
Or is Pulumi respecting the dependency but the ec2 resource has been created but the vm is not available for connection yet?fancy-eve-82724
07/04/2024, 3:03 PMdepends_on
constraint, correctfancy-eve-82724
07/04/2024, 3:03 PMadmin_server
has not been created at all at this pointdry-keyboard-94795
07/04/2024, 3:03 PMadventurous-butcher-54166
07/04/2024, 3:06 PMfancy-eve-82724
07/04/2024, 3:06 PMv3.32.1
adventurous-butcher-54166
07/04/2024, 3:06 PM3.122.0
- try updatingfancy-eve-82724
07/04/2024, 3:07 PMfancy-eve-82724
07/04/2024, 3:10 PMadventurous-butcher-54166
07/04/2024, 3:12 PMconfig:
pulumi:disable-default-providers:
- docker
adventurous-butcher-54166
07/04/2024, 3:13 PMfancy-eve-82724
07/04/2024, 3:14 PMdry-keyboard-94795
07/04/2024, 3:15 PMfancy-eve-82724
07/04/2024, 3:16 PMfancy-eve-82724
07/04/2024, 3:16 PMadventurous-butcher-54166
07/04/2024, 3:17 PM--logflow -v*=*10
?fancy-eve-82724
07/04/2024, 3:17 PMadventurous-butcher-54166
07/04/2024, 3:19 PMfancy-eve-82724
07/04/2024, 3:20 PMadmin_docker = docker.Provider(
"docker-admin",
host=admin_eip.public_ip.apply(
lambda l: f"<ssh://ec2-user>@{l}"
),
opts=pulumi.ResourceOptions(
parent=admin_server,
depends_on=[admin_server]
)
)
So in this case, the elastic IP had been created, but the EC2 instance had not been created.fancy-eve-82724
07/04/2024, 3:20 PMfancy-eve-82724
07/04/2024, 3:21 PMdepends_on
constraint though.dry-keyboard-94795
07/04/2024, 3:21 PMdry-keyboard-94795
07/04/2024, 3:21 PMdry-keyboard-94795
07/04/2024, 3:22 PMfancy-eve-82724
07/04/2024, 3:22 PMdry-keyboard-94795
07/04/2024, 3:23 PMfancy-eve-82724
07/04/2024, 3:24 PMadmin_server.public_ip
will change once the EIP is associated with it.adventurous-butcher-54166
07/04/2024, 3:24 PMdry-keyboard-94795
07/04/2024, 3:25 PMdry-keyboard-94795
07/04/2024, 3:26 PMfancy-eve-82724
07/04/2024, 3:26 PMadventurous-butcher-54166
07/04/2024, 3:31 PMpulumi up
operation would be to initialize the docker provider in a callback to admin_server.instance_state
output, preferrably when it returns "`running`"adventurous-butcher-54166
07/04/2024, 3:32 PMfancy-eve-82724
07/04/2024, 3:32 PMfancy-eve-82724
07/04/2024, 3:34 PMdry-keyboard-94795
07/04/2024, 3:43 PMfancy-eve-82724
07/04/2024, 3:44 PMdry-keyboard-94795
07/04/2024, 3:45 PMfancy-eve-82724
07/04/2024, 3:45 PMdry-keyboard-94795
07/04/2024, 3:49 PMhost=pulumi.Output.all(admin_eip.public_ip, admin_server.id).apply(lambda args: f"{<ssh://ec2-user@{args[0]}")|ssh://ec2-user@{args[0]}")>
fancy-eve-82724
07/04/2024, 4:16 PM