https://github.com/willshersystems/ansible-sshd

Ansible role to configure the OpenSSH server daemon
https://github.com/willshersystems/ansible-sshd

ansible openssh openssh-server ssh sshd

Last synced: 3 months ago
JSON representation

Ansible role to configure the OpenSSH server daemon

• Host: GitHub
• URL: https://github.com/willshersystems/ansible-sshd
• Owner: willshersystems
• License: lgpl-3.0
• Created: 2014-12-18T22:23:10.000Z (over 9 years ago)
• Default Branch: main
• Last Pushed: 2024-03-15T11:16:21.000Z (3 months ago)
• Last Synced: 2024-03-15T12:35:19.725Z (3 months ago)
• Topics: ansible, openssh, openssh-server, ssh, sshd
• Language: HTML
• Homepage: https://galaxy.ansible.com/willshersystems/sshd
• Size: 459 KB
• Stars: 223
• Watchers: 13
• Forks: 134
• Open Issues: 10
• Metadata Files:
  • Readme: README-ostree.md
  • Changelog: CHANGELOG.md
  • Contributing: contributing.md
  • License: LICENSE
  • Code of conduct: CODE_OF_CONDUCT.md

Lists

• awesome-list-ansible - ansible-sshd

README

        
# rpm-ostree

The role supports running on [rpm-ostree](https://coreos.github.io/rpm-ostree/)

systems. The primary issue is that the `/usr` filesystem is read-only, and the

role cannot install packages. Instead, it will just verify that the necessary

packages and any other `/usr` files are pre-installed. The role will change the

package manager to one that is compatible with `rpm-ostree` systems.

## Building

To build an ostree image for a particular operating system distribution and

version, use the script `.ostree/get_ostree_data.sh` to get the list of

packages. If the role uses other system roles, then the script will include the

packages for the other roles in the list it outputs.  The list of packages will

be sorted in alphanumeric order.

Usage:

```bash

.ostree/get_ostree_data.sh packages runtime DISTRO-VERSION FORMAT

```

`DISTRO-VERSION` is in the format that Ansible uses for `ansible_distribution`

and `ansible_distribution_version` - for example, `Fedora-38`, `CentOS-8`,

`RedHat-9.4`

`FORMAT` is one of `toml`, `json`, `yaml`, `raw`

* `toml` - each package in a TOML `[[packages]]` element

```toml

[[packages]]

name = "package-a"

version = "*"

[[packages]]

name = "package-b"

version = "*"

...

```

* `yaml` - a YAML list of packages

```yaml

- package-a

- package-b

...

```

* `json` - a JSON list of packages

```json

["package-a","package-b",...]

```

* `raw` - a plain text list of packages, one per line

```bash

package-a

package-b

...

```

What format you choose depends on which image builder you are using.  For

example, if you are using something based on

[osbuild-composer](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/composing_installing_and_managing_rhel_for_edge_images/index#creating-an-image-builder-blueprint-for-a-rhel-for-edge-image-using-the-command-line-interface_composing-a-rhel-for-edge-image-using-image-builder-command-line),

you will probably want to use the `toml` output format.