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

the file provisioner doesn't support ~/foo #1559

Closed
failshell opened this issue Apr 16, 2015 · 4 comments · Fixed by #1569
Closed

the file provisioner doesn't support ~/foo #1559

failshell opened this issue Apr 16, 2015 · 4 comments · Fixed by #1569

Comments

@failshell
Copy link

The file provisioner doesn't seem to understand the ~ path.

With the following config:

  provisioner "file" {
    source = "~/bar"
    destination = "~/bar"
  }

I get the folllowing error:

* stat ~/bar: no such file or directory
* 1 error(s) occurred:

I'm guessing something like 1339 is needed.

@failshell failshell changed the title the file provisioner doesn' the file provisioner doesn't support ~/foo Apr 16, 2015
@phinze
Copy link
Contributor

phinze commented Apr 16, 2015

Thanks for the report - we'll get this looked at - shouldn't be too bad.

@arubis
Copy link

arubis commented Apr 16, 2015

I've been working around this by specifying absolute paths (including in accompanying usage documentation), but would love to see this improvement!

@mitchellh
Copy link
Contributor

We added this feature to remote-exec so it shouldn't be hard to do for file. Will do!

phinze added a commit that referenced this issue Apr 16, 2015
closes #1559

tested manually, since a unit test would be sort of annoying to write.
:)
@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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants