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

No access to remote host name in local.transfer() #140

Open
ravi opened this issue Jun 2, 2016 · 5 comments
Open

No access to remote host name in local.transfer() #140

ravi opened this issue Jun 2, 2016 · 5 comments
Labels

Comments

@ravi
Copy link

ravi commented Jun 2, 2016

Perhaps this is a poor usage pattern, but I have a need to access the remote host name or at least the target name, in transfer() (the files to be transferred are based on the remote hostname or target). In earlier versions I could do this using something like local.flight.flightplan.target.destination (IIRC) but now I don't have that (I could fudge using local._context.target but I am guessing underscore prefixed properties should be treated as private following Unix conventions).

I am wondering if this may be a general need, not just a peculiarity of my usage :-).

@pstadler
Copy link
Owner

pstadler commented Jun 2, 2016

See this section in the docs: https://github.com/pstadler/flightplan#accessing-runtime-information

Is this what you're asking for?

@ravi
Copy link
Author

ravi commented Jun 3, 2016

For local.transfer() (IIUC) even though there is a remote end, that info is not accessible via the runtime. But I came up with a workaround using plan.runtime.target for my current need. Thank you for the response.

@ravi ravi closed this as completed Jun 3, 2016
@ravi
Copy link
Author

ravi commented May 15, 2017

I am bumping up against this issue once again. @pstadler is there an easy way to accomplish this? My guess is not? Because the looping over the target hosts occurs within the local.transfer(), but I thought I'd ask to be sure.

@ravi ravi reopened this May 15, 2017
@pstadler
Copy link
Owner

pstadler commented May 15, 2017 via email

@pstadler
Copy link
Owner

Ah sorry, I thought this is about another ticket. This is indeed hard to solve. Maybe you should simply roll with an own implementation running rsync in a local loop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants