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

[RFE] make mayday config input and targz output more flexible #1182

Open
vbatts opened this issue Sep 19, 2023 · 1 comment
Open

[RFE] make mayday config input and targz output more flexible #1182

vbatts opened this issue Sep 19, 2023 · 1 comment
Labels
kind/feature A feature request

Comments

@vbatts
Copy link
Member

vbatts commented Sep 19, 2023

Current situation

Use-case is to use mayday more broadly than just for flatcar.
Like scp mayday mylinuxhost:/tmp/ && ssh mylinuxhost /tmp/mayday to quickly get the collection from the machine.

Impact

currently it requires both the config file to be local and then outputs the collection to a local path.
This means copying over a couple files, and then back another file. Not a big deal, but a couple moving parts.

Ideal future situation

I'm thinking that taking the config data in on stdin, and then outputting the tarball to stdout would be straightforward enough.

Additional information

maybe other ideas?

@pothos
Copy link
Member

pothos commented Sep 19, 2023

maybe other ideas?

When mayday would generate shell commands to execute (mayday | ssh host > output), it wouldn't even be needed as binary on the remote host. Another way is to make it an ssh wrapper like mayday --output /tmp/out ssh host and then it could copy itself over first before execution (or here again, use shell commands instead of a binary).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature A feature request
Projects
Development

No branches or pull requests

2 participants