Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sys
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 20
    • Issues 20
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • CHEF
  • cookbooks
  • sys
  • Issues
  • #14

Closed
Open
Created May 29, 2020 by Christopher Huhn@c.huhn🥚Owner

node['sys']['ssh']['config'] and node['sys']['ssh']['ssh_config'] handle options differently

node['sys']['ssh']['config'] takes a hash as config:

{ host_pattern1: { key: value, … }, … }

In contrast node['sys']['ssh']['ssh_config'] takes an array as config:

[ {host_pattern1: { key: value, … }}, … ]

I see no reason to have the same host pattern multiple times w/o merging.

OTOH ordering may be relevant (→ array).

Anyhow these attributes should behave similar.

Edited May 29, 2020 by Christopher Huhn
Assignee
Assign to
Time tracking

https://git.gsi.de is provided by CIT-HPC | GSI Helmholtzzentrum fuer Schwerionenforschung GmbH | Imprint (in German) | Privacy policy