adamant-leather-41068
12/07/2022, 4:52 AMcloudinit
.
If I change this data, Pulumi correctly identified the resources affected and shutsdown the correct EC2 instances. However, it doesn't write the new config data, so when it starts up the machines the old versions are still there.
If I manually terminate the EC2 instances, then run pulumi refresh
and pulumi up
it all works.
What am I doing wrong?millions-furniture-75402
12/07/2022, 2:17 PMadamant-leather-41068
12/08/2022, 12:20 AMwrite_files: [
{
permissions: '0644',
path: '/root/conf/storage-node.env',
// this writes the .env file from what has been loaded
content: Object.entries({ ...nodeConfig })
.map(([key, value]) =>
`${key.trim().replace(/[A-Z]/g, s => `_${s}`).toUpperCase()}=${value}`)
.join('\n')
}
{
permissions: '0664',
path: '/root/conf/haproxyconf/haproxy.cfg',
content: haProxyCFG,
}
]
Specifically the storage-node.env
isn't getting updated.millions-furniture-75402
12/08/2022, 2:03 PMadamant-leather-41068
12/10/2022, 6:07 AMmillions-furniture-75402
12/11/2022, 8:17 PM