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
I have encountered an error in line 474 with the null_resource related to not finding the path to the \bin\bash within the environment where the system should be running.
I have tried multiple alternatives but it doesn't seem to work.
It looks like you're deploying on Windows, which is causing the null_resource to fail since /bin/bash isn’t available in %PATH%. Since Windows does not have /bin/bash by default, the script is unable to execute as expected. To fix this, try deploying via GitHub Actions, as the workflows run on Ubuntu, where /bin/bash is available. Alternatively, you can use WSL or a Linux-based environment.
I have encountered an error in line 474 with the null_resource related to not finding the path to the \bin\bash within the environment where the system should be running.
I have tried multiple alternatives but it doesn't seem to work.
The code:
_```
resource "null_resource" "rds_endpoint" {
provisioner "local-exec" {
command = <<EOF
RDS_URL="${aws_db_instance.database-instance.endpoint}"
RDS_URL=$${RDS_URL::-5}
sed -i "s,RDS_ENDPOINT_VALUE,$RDS_URL,g" ${path.module}/resources/ecs/task_definition.json
EOF
interpreter = ["/bin/bash", "-c"]
}
depends_on = [
aws_db_instance.database-instance
]
}
The text was updated successfully, but these errors were encountered: