Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config: interprets '~' as the current user home dir in file() #1338

Merged
merged 1 commit into from
Mar 30, 2015

Conversation

7heo
Copy link
Contributor

@7heo 7heo commented Mar 30, 2015

No description provided.

@phinze
Copy link
Contributor

phinze commented Mar 30, 2015

LGTM. Congratulations on your first Terraform contribution! 🎉

phinze added a commit that referenced this pull request Mar 30, 2015
config: interprets '~' as the current user home dir in file()
@phinze phinze merged commit f9d9261 into hashicorp:master Mar 30, 2015
@nathanleiby
Copy link

thanks @7heo - one small tilde, but oh so much lovelier to work with

@7heo
Copy link
Contributor Author

7heo commented Mar 31, 2015

@nathanleiby I couldn't have done what I'm needing without it, to be honest. I's rather sweet to have

resource "google_compute_instance" "default" {
[...]
    metadata {
        sshKeys = "${var.ssh_user}:${file(\"~/.ssh/id_rsa.pub\")}"
    }

    provisioner "local-exec" {
        command = "./bootstrap_chef.sh ${var.ssh_user} ${google_compute_instance.default.network_interface.0.access_config.0.nat_ip}"
    }
[...]
}

working :)

It is SO much cleaner than having to wrap terraform in a shell script just for that purpose... So yeah I'm very glad it works, and I'm even happier that 0.4.0 gets released soon.

@ghost
Copy link

ghost commented May 3, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators May 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants