view modules/sshkeys_core/README.md @ 466:202aeef575a1

Correct HTTP log paths in LogWatch It wasn't generating logs because we're not using the normal pattern - our site name comes _after_ the "access" part, not before
author IBBoard <dev@ibboard.co.uk>
date Sun, 25 Feb 2024 10:10:32 +0000
parents 750d36241580
children adf6fe9bbc17
line wrap: on
line source


# sshkeys_core

## Table of Contents

1. [Description](#description)
2. [Usage - Configuration options and additional functionality](#usage)
3. [Reference - User documentation](#reference)
4. [Development - Guide for contributing to the module](#development)

<a id="description"></a>
## Description

Manage SSH `authorized_keys`, and `ssh_known_hosts` files.

<a id="usage"></a>
## Usage

To manage an authorized key for a user, use the following code:

```
ssh_authorized_key { 'nick@magpie.example.com':
  ensure => present,
  user   => 'nick',
  type   => 'ssh-rsa',
  key    => 'AAAAB3Nza[...]qXfdaQ==',
}
```

To manage a known hosts file entry, use the following code:

```
sshkey { 'github.com':
  ensure => present,
  type   => 'ssh-rsa',
  key    => 'AAAAB3Nza[...]UFFAaQ==',
}
```
<a id="reference"></a>
## Reference

Please see REFERENCE.md for the reference documentation.

This module is documented using Puppet Strings.

For a quick primer on how Strings works, please see [this blog post](https://puppet.com/blog/using-puppet-strings-generate-great-documentation-puppet-modules) or the [README.md](https://github.com/puppetlabs/puppet-strings/blob/master/README.md) for Puppet Strings.

To generate documentation locally, run the following command:
```
bundle install
bundle exec puppet strings generate ./lib/**/*.rb
```
This command will create a browsable `\_index.html` file in the `doc` directory. The references available here are all generated from YARD-style comments embedded in the code base. When any development happens on this module, the impacted documentation should also be updated.

<a id="development"></a>
## Development

Puppet Labs modules on the Puppet Forge are open projects, and community contributions are essential for keeping them great. We can't access the huge number of platforms and myriad of hardware, software, and deployment configurations that Puppet is intended to serve.

We want to keep it as easy as possible to contribute changes so that our modules work in your environment. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.

For more information, see our [module contribution guide.](https://puppet.com/docs/puppet/latest/contributing.html)