No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Background: I'm trying to populate `cloud-init` data, and specifically to provide `pp_uuid` to encode machine UUID in the puppet certificate <https://cloudinit.readthedocs.io/en/latest/topics/modules.html#puppet>

If the UUID is assigned by the provider when the instance is created, it is not possible to use the value in an another property on the same resource.

I think openstack has a metadata service for instances to query data, so you could use that within your user-data script?

Hm, I'm trying to populate cloud-init, but maybe it has some support for querying metadata

Oh, nice, cloud-init apparently is able to get the data dynamically

No, I didn't find a way to feed the machine uuid into the proper field for puppet...

Per <https://docs.openstack.org/nova/latest/user/metadata.html#openstack-format-metadata>, you can get the instance uuid from `<http://169.254.169.254/openstack/2018-08-27/meta_data.json>`. So `uuid=$(curl <http://169.254.169.254/openstack/2018-08-27/meta_data.json> | jq -r .uuid)` would provide a uuid you could use in a startup script.

Yeah, but the file I'd need to write to is again YAML, which means second line needs to get an indent, and from my experiments so far trying to encode in yaml a bash script writing out yaml ended up with `cloud-init` deciding it doesn't like that part of the configuration