Having "password" defined with newparam, any Content of Type Sensitive will lead to
"Unable to mark 'password' as sensitive: password is a parameter and not a property, and cannot be automatically redacted."

In Fact "password" (as well as others) should be a Property.
(compare https://puppet.com/docs/puppet/7/custom_types.html#tandp_properties_and_parameters)

…debian_8_support

pdksync - (IAC-1598) - Remove Support for Debian 8

Fix "password" as Property

…ky_8_support

pdksync - (IAC-1751) - Add Support for Rocky 8

…alinux_8_support

pdksync - (IAC-1753) - Add Support for AlmaLinux 8

change the honeycomb writekey to a github secret

move honeycomb key

…centos_6_support

pdksync - (IAC-1787) Remove Support for CentOS 6

The git prefix is no longer deemed secure for our setup, swapping to https

(maint) pr_test workflow fix

A temporary fix for an issue for chocolatey. Error seems to originate from a problem with the boxes(?)

(GH-388) Temporary Windows Fix

…e_ubuntu_16.04_support

pdksync - (GH-iac-334) Remove Support for Ubuntu 14.04/16.04

pdksync - Add labeller and stale GHA workflows

…gf3911d3

pdksync - pdksync_heads/main-0-gf3911d3

The current implementation only allows you to pass a file name to the certificate
and private_key parameters. When you are fetching certificates from vault or another secure store,
you'll first have to save them to a file. This is very innconveniant.

This PR add's the parameters certificate_content and private_key_content. These parameters
are mutually exclusive from their file counterparts.

With this change, you can now fetch a certificate and/or a password from vault
(through a hiera lookup for example) and use it directly on the type.

Because these values can be sensitive, both of the new parameters support
passing the value as a sensitive data type.

…icate_content

Add support for certificate_content and private_key_content parameters

…equest_target"

…est_target

pdksync - PDKSYNC Update labeller trigger

Release prep v4.3.0