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

Keyboard provisioning for inline shell commands #61408

Closed
mcandre opened this issue Aug 27, 2019 · 3 comments
Closed

Keyboard provisioning for inline shell commands #61408

mcandre opened this issue Aug 27, 2019 · 3 comments
Labels
affects_2.9 This issue/PR affects Ansible v2.9 commands Commands category feature This issue/PR relates to a feature request. module This issue/PR relates to a module. support:core This issue/PR relates to code supported by the Ansible Engineering Team.

Comments

@mcandre
Copy link

mcandre commented Aug 27, 2019

SUMMARY

Legacy targets such as DOS do not support sshd, nor do they provide reliable telnetd access. For these targets, it would be perhaps more convenient to operate the target in a VM, and send provisioning via the hypervisor's keyboard emulator, similar to boot_command in Packer scripts.

Could we get a similar mechanism for Ansible, that would plugin naturally to Vagrantfile's, allowing these older systems to be provisioned with hypervisor keyboard commands?

ISSUE TYPE
  • Feature Idea
COMPONENT NAME

shell

ADDITIONAL INFORMATION

Workaround when sshd is unavailable and telnetd is either unavailable, corrupts user input, and/or blocks other networking provisioning applications (ping, hget, wget, curl, ftp, nc, etc.) from succeeding.

@ansibot
Copy link
Contributor

ansibot commented Aug 27, 2019

Files identified in the description:

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

@ansibot ansibot added affects_2.9 This issue/PR affects Ansible v2.9 commands Commands category feature This issue/PR relates to a feature request. module This issue/PR relates to a module. needs_triage Needs a first human triage before being processed. support:core This issue/PR relates to code supported by the Ansible Engineering Team. labels Aug 27, 2019
@bcoca bcoca removed the needs_triage Needs a first human triage before being processed. label Aug 29, 2019
@ansibot
Copy link
Contributor

ansibot commented May 16, 2020

Files identified in the description:

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help

@bcoca
Copy link
Member

bcoca commented Mar 5, 2021

Hi!

Thanks very much for your submission to Ansible. It sincerely means a lot to us that you've taken time to contribute.

Unfortunately, we are going to decline this request because aside from the complexity of implementation (also need to add file transfers and bidrectional communication by hacking the hypervisor) and there is no real demand for this feature.

However, we're absolutely always up for discussion.
Since this is a really busy project, we don't always see comments on closed tickets, but want to encourage open dialog.

You can stop by the development list, and we'd be glad to talk about it - and we might even be persuaded otherwise!

In the future, sometimes starting a discussion on the development list prior to implenting a feature can make getting things included a little easier, but it's not always necessary.

Thank you once again for this and your interest in Ansible!

@bcoca bcoca closed this as completed Mar 5, 2021
@ansible ansible locked and limited conversation to collaborators Apr 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.9 This issue/PR affects Ansible v2.9 commands Commands category feature This issue/PR relates to a feature request. module This issue/PR relates to a module. support:core This issue/PR relates to code supported by the Ansible Engineering Team.
Projects
None yet
Development

No branches or pull requests

3 participants