We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
path
i'm trying to create a bunch of directories in one step, but have not yet understood what path exactly does.
i've set it once in section context and once in step context, then i shell out inside a ruby_command like so:
section
step
ruby_command
step "Create local directory structure" do path @clients_dir ruby_command do command "mkdir -p #{@single_client_dir}/{themes,migration,plugins,migration/#{@domain}}" end end
i expect the directory to be created in @clients_dir but it gets created inside the runbook directory.
is path only the context for ruby commands and not shell commands, i.e. should i do something like FileUtils.makedir_p?
FileUtils.makedir_p
UPDATE: tried that, also does not create the directories in the context of path, but in the cwd of the runbook.
ps: maybe you can activate 'Discussions' for this repo, so this info could get collected in some sort of forum rather than issues.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
i'm trying to create a bunch of directories in one step, but have not yet understood what
path
exactly does.i've set it once in
section
context and once instep
context, then i shell out inside aruby_command
like so:i expect the directory to be created in @clients_dir but it gets created inside the runbook directory.
is
path
only the context for ruby commands and not shell commands, i.e. should i do something likeFileUtils.makedir_p
?UPDATE: tried that, also does not create the directories in the context of
path
, but in the cwd of the runbook.ps: maybe you can activate 'Discussions' for this repo, so this info could get collected in some sort of forum rather than issues.
The text was updated successfully, but these errors were encountered: