All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org).
+## [v2.4.0](https://github.com/puppetlabs/puppetlabs-sshkeys_core/tree/v2.4.0) (2023-02-14)
+
+[Full Changelog](https://github.com/puppetlabs/puppetlabs-sshkeys_core/compare/v2.3.0...v2.4.0)
+
+### Added
+
+- \(MODULES-11371\) Updates PDK template [\#67](https://github.com/puppetlabs/puppetlabs-sshkeys_core/pull/67) ([mhashizume](https://github.com/mhashizume))
+
## [v2.3.0](https://github.com/puppetlabs/puppetlabs-sshkeys_core/tree/v2.3.0) (2021-10-04)
[Full Changelog](https://github.com/puppetlabs/puppetlabs-sshkeys_core/compare/2.2.0...v2.3.0)
The following parameters are available in the `ssh_authorized_key` type.
-* [`drop_privileges`](#drop_privileges)
-* [`name`](#name)
-* [`provider`](#provider)
+* [`drop_privileges`](#-ssh_authorized_key--drop_privileges)
+* [`name`](#-ssh_authorized_key--name)
+* [`provider`](#-ssh_authorized_key--provider)
-##### <a name="drop_privileges"></a>`drop_privileges`
+##### <a name="-ssh_authorized_key--drop_privileges"></a>`drop_privileges`
-Valid values: ``true``, ``false``, `yes`, `no`
+Valid values: `true`, `false`, `yes`, `no`
Whether to drop privileges when writing the key file. This is
useful for creating files in paths not writable by the target user. Note
the possible security implications of managing file ownership and
permissions as a privileged user.
-Default value: ``true``
+Default value: `true`
-##### <a name="name"></a>`name`
+##### <a name="-ssh_authorized_key--name"></a>`name`
namevar
if you want to specify one key for multiple users, you must use a different
comment for each instance.
-##### <a name="provider"></a>`provider`
+##### <a name="-ssh_authorized_key--provider"></a>`provider`
The specific backend to use for this `ssh_authorized_key` resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
The following parameters are available in the `sshkey` type.
-* [`name`](#name)
-* [`provider`](#provider)
-* [`type`](#type)
+* [`name`](#-sshkey--name)
+* [`provider`](#-sshkey--provider)
+* [`type`](#-sshkey--type)
-##### <a name="name"></a>`name`
+##### <a name="-sshkey--name"></a>`name`
namevar
The host name that the key is associated with.
-##### <a name="provider"></a>`provider`
+##### <a name="-sshkey--provider"></a>`provider`
The specific backend to use for this `sshkey` resource. You will seldom need to specify this --- Puppet will usually
discover the appropriate provider for your platform.
-##### <a name="type"></a>`type`
+##### <a name="-sshkey--type"></a>`type`
Valid values: `ssh-dss`, `ssh-ed25519`, `ssh-rsa`, `ecdsa-sha2-nistp256`, `ecdsa-sha2-nistp384`, `ecdsa-sha2-nistp521`, `sk-ecdsa-sha2-nistp256@openssh.com`, `sk-ssh-ed25519@openssh.com`, `dsa`, `ed25519`, `rsa`, `ecdsa-sk`, `ed25519-sk`