This message was deleted.

It takes a moment to really "get" the Pulumi outputs. Once you do it, you have at your disposal the full power of (in this case) Go. Taking the example gist, I think the problem lies here

ipv4Address := ipv4.IpAddress.ApplyT(func(val string) string {
		return val
	})

This will NOT do what you think it will do. The return type of ApplyT is still a pulumi.Output. Only inside the closure (the func passed to ApplyT) the type is a plain string...

Thanks for these useful hints

When I was in the process of ditching Go for Py (because of outputs) I was thinking that maybe channels would be a better (?) abstraction for async nature of outputs? Anyhow, this is how All and Apply work for a task of generating the files using the native types (I know this is in Py, but the concept doesn’t change, just gets awfully verbose with Go)

yaml_done = kubeone_cluster.render_yaml(
    cp_host=cp_fip.address,
    cp_int_ip=cp_inst.access_ip_v4,
    cp_hostname=cp_inst.name,
    static_workers=worker_instances,
)

# renderYAML waits for outputs to be ready
# and renders the kubeone_cluster to a YAML file
def render_yaml(
    cp_host, cp_int_ip, cp_hostname, static_workers: List[compute.Instance]
) -> pulumi.Output[bool]:
    def populate_spec(outputs):
        kubeone_cluster["apiEndpoint"]["host"] = outputs["cp_host"]
        kubeone_cluster["controlPlane"]["hosts"][0]["publicAddress"] = outputs[
            "cp_host"
        ]
        kubeone_cluster["controlPlane"]["hosts"][0]["hostname"] = outputs["cp_hostname"]
        kubeone_cluster["controlPlane"]["hosts"][0]["privateAddress"] = outputs[
            "cp_int_ip"
        ]

        for worker_out in outputs["workers_output"]:
            kubeone_cluster["staticWorkers"]["hosts"].append(
                {
                    "publicAddress": worker_out[0],
                    "privateAddress": worker_out[0],
                    "sshUsername": "root",
                    "hostname": worker_out[1],
                    "bastion": outputs["cp_host"],
                }
            )

        # writing kubeone yaml to file
        with open("kubeone.yaml", "w") as f:
            yaml.dump(
                kubeone_cluster,
                f,
                sort_keys=False,
            )

        return True

PS. It still boggles me that none of that is linked from the outputs docs to a blog post or smth. This is table stakes to many, it seems.

Haha, initially I have been playing with kubeone as well... Now I "just" want to create some cloud resources and run ansible to manage the vm configuration. I think I will link the repo to get some feedback for following better practice in pulumi... It doesn't feel really right how I got it now.