add vars for prefix and user and project name #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 5 commits
March 15, 2018 22:39
Add ssh_config_host_prefix and ssh_config_default_user
add ssh_config_force_user ssh_config_default_user ssh_config_host_prefix
add ssh_config_project_name for multiple project use
add ssh_config_project_name for multiple project use
add ssh_config_force_user ssh_config_default_user ssh_config_host_prefix ssh_config_project_name
russStarr
reviewed
Mar 31, 2018
| @@ -39,6 +39,11 @@ Role Variables | |||
| |`ssh_config_file`|`{{ssh_configs_dir}}/ssh_config`|Where should the SSH client configuration be written to? Most implementations use `~/.ssh/config` so you can change this if you want.| | |||
| |`inventory_groups`|`["all"]`|Which inventory groups should we read to create SSH client configuration for? By default the built-in group `all` will be used since it should always be valid. `ungrouped` is also a built-in group name. To get a full list of groups in your Ansible directory, use `ansible -m debug -a 'var=groups.keys()\|sort' localhost`.| | |||
| |`keepgroupnames`|`"False"`|Should ansible groupname(s) be used to create a pattern for hostname ? When a server is part of several groups, then additionnal patterns will be created to match each and every group. When set to `"True"` and with inventory file example below, `ssh server1` **and** `ssh production.server1` will both work.| | |||
| | `ssh_config_project_name` | `` | Project name for use in marker. | | |||
| | `ssh_config_host_prefix` | `` | Prefix for add to hostname. | | |||
There was a problem hiding this comment.
I'm not completely understanding the use case for a host prefix. Can you elaborate more? It sounds like something specific to your environment maybe?
There was a problem hiding this comment.
On some servers I use two different logins.
one with root rights.
and the second for working with the deployed application
and I connect to them in different ways, for example:
ssh rapp # for rott access
ssh app # for app user access
russStarr
reviewed
Mar 31, 2018
| @@ -39,6 +39,11 @@ Role Variables | |||
| |`ssh_config_file`|`{{ssh_configs_dir}}/ssh_config`|Where should the SSH client configuration be written to? Most implementations use `~/.ssh/config` so you can change this if you want.| | |||
| |`inventory_groups`|`["all"]`|Which inventory groups should we read to create SSH client configuration for? By default the built-in group `all` will be used since it should always be valid. `ungrouped` is also a built-in group name. To get a full list of groups in your Ansible directory, use `ansible -m debug -a 'var=groups.keys()\|sort' localhost`.| | |||
| |`keepgroupnames`|`"False"`|Should ansible groupname(s) be used to create a pattern for hostname ? When a server is part of several groups, then additionnal patterns will be created to match each and every group. When set to `"True"` and with inventory file example below, `ssh server1` **and** `ssh production.server1` will both work.| | |||
| | `ssh_config_project_name` | `` | Project name for use in marker. | | |||
There was a problem hiding this comment.
I would like to stick with using the group as the marker as "project name" seems too implementation specific. Maybe there just needs to be a generic variable for modifying the marker so someone could add anything they want.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.