Allow ssh_config
generation to be disabled for Machine ID Identity Output
#40776
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.
We currently allow the Identity Output to be used to provide credentials for two main use-cases:
However, we always try to generate the ssh_config needed for SSH access. This is problematic for a few reasons:
tbot
instance may run close to the auth server and it may be intended for this instance to come online before proxies are available.As such, I've added an
ssh_config
option which can be set toon
oroff
. If unspecified, it defaults to the behaviour we've had historically (on
).example:
changelog: Add the ability to control
ssh_config
generation in Machine ID's Identity Outputs. This allows the generation of thessh_config
to be disabled if unnecessary, improving performance and removing the dependency on the Proxy being online.