Date   

Re: Facter 4 pre-release

Ewoud Kohl van Wijngaarden
 

On Wed, Feb 26, 2020 at 04:00:03PM +0200, Bogdan Irimie wrote:
We are very happy to inform you that in the last week we have deployed a
pre-release version of Facter 4 to rubygems. Facter 4
<https://github.com/puppetlabs/facter-ng>; is still under development and
our first goal is to replace Facter 2.x in Puppet gem with Facter 4.

Starting with Puppet 6.13.0 gem users can opt in to use Facter 4.

To try out Facter 4 you can run: *gem install facter –pre*

We are planning to do a full release of Facter 4 gem on the 11th of March
2020.

Impact:

-

Module tests that have been converted to Limus and run with Puppet as a
gem will work once https://tickets.puppetlabs.com/browse/IAC-551 is
resolved.
-

Modules converted to litmus that use litmus:install_agent or beaker with
agent provisioning will not be affected as we still plan to provide Facter
3 as the default facter in Puppet Agent AIO.
What I miss is what the impact for me as a module author. This only mentions litmus (which I don't use), so there's no impact? The README states it's a 100% compatible drop-in replacement. Does that mean that legacy facts are also still supported?

We're heavy users of https://github.com/mcanevet/rspec-puppet-facts and it would be nice if there were simple instructions to verify modules with Facter 4 facts.


PDK 1.17.0 now available

Jesse Scott
 

Hello!

The Puppet Developer Experience team is pleased to announce the latest release of the Puppet Development Kit (PDK), version 1.17.0.

Highlights from the 1.17.0 release include:

- PDK functionality can now be modified by feature flags (which is going to be more notable when you get to the next bullet point). You can see what flags are available using the `pdk get config` command.

- PDK can now validate control repositories! This is a new feature and currently requires the `controlrepo` feature flag to be set. In a future release this feature will be enabled by default.

As of PDK 1.17.0 we are now packaging PDK for macOS 10.15 and have stopped packaging PDK for macOS 10.11 and 10.12.

Reminder: Since PDK 1.14.1, use of the PDK with Ruby versions prior to 2.4.0 is deprecated and a warning will be issued. PDK 1.17.0 is still fully functional back to Ruby 2.1.9 however we are projecting a PDK 2.0.0 release in early 2020 which will eliminate support for Ruby < 2.4.0.

You can review the full release notes at: https://puppet.com/docs/pdk/1.x/release_notes_pdk.html#release-notes-pdk-x.17

To install or upgrade to this new version, use your platform's package manager (see https://puppet.com/docs/pdk/1.x/pdk_install.html) or download the packages directly for Windows, macOS, and Linux platforms at https://puppet.com/download-puppet-development-kit.

Thanks!


Facter 4 pre-release

Bogdan Irimie
 

Hi,


We are very happy to inform you that in the last week we have deployed a pre-release version of Facter 4 to rubygems. Facter 4 is still under development and our first goal is to replace Facter 2.x in Puppet gem with Facter 4.


Starting with Puppet 6.13.0 gem users can opt in to use Facter 4.

To try out Facter 4 you can run: gem install facter –pre


We are planning to do a full release of Facter 4 gem on the 11th of March 2020. 


Impact:

  • Module tests that have been converted to Limus and run with Puppet as a gem will work once https://tickets.puppetlabs.com/browse/IAC-551 is resolved.

  • Modules converted to litmus that use litmus:install_agent or beaker with agent provisioning will not be affected as we still plan to provide Facter 3 as the default facter in Puppet Agent AIO.


 

If you have any questions or feedback, please feel free to reach out on slack or open a ticket on https://tickets.puppetlabs.com/projects/FACT with facter-ng label. 



Re: PDK 1.16.0 now available

Jesse Scott
 

[sad trombone]

It turns out the macOS package manager doesn't update the permissions of existing files if that is the only change, so if you have previously installed the broken package (1.16.0.1) you will need to completely uninstall the old package before installing the fixed package (1.16.0.2).

Read below for instructions on how to uninstall/reinstall. 

Please let us know if you are still having problems by filing an issue on the PDK repo: https://github.com/puppetlabs/pdk/issues/new/choose


If you install PDK on macOS via Homebrew, run:

brew cask uninstall pdk
sudo rm -rf /opt/puppetlabs/pdk
brew cask install puppetlabs/puppet/pdk

and you should be all fixed.

----------------

If you install PDK on macOS manually, run:

sudo rm -rf /opt/puppetlabs/pdk
sudo pkgutil --forget com.puppetlabs.pdk

then download and install the latest PDK packages (make sure you get 1.16.0.2) as normal.



On Tue, Feb 11, 2020 at 10:12 AM Jesse Scott <jesse@...> wrote:
On macOS, there was a permissions issue in the PDK 1.16.0 packages (released as PDK 1.16.0.1) which prevented most PDK commands from executing.

PDK 1.16.0.2, a new release that addresses the permissions issue, is now available. This release contains no other changes.

We're sorry for the inconvenience of the broken release and we have added additional package acceptance tests to catch this issue in the future.

On Thu, Feb 6, 2020 at 11:12 AM Puppet Product Updates <puppet-product-updates@...> wrote:
Hello!

The Puppet Developer Experience team is pleased to announce the latest release of the Puppet Development Kit (PDK), version 1.16.0.

Highlights from the 1.16.0 release include:

 - Added a new "use_litmus" setting for auto-generated Travis CI configurations to make it easier to adopt Puppet Litmus in your module CI pipelines.
- PDK will now correctly place new files based on the root of your module even if you invoke `pdk new` from within a subdirectory of your module.
- To ensure that modules are compatible with all Puppet Masters regardless of their locale, `pdk module build` will now reject files that contain non-ASCII characters in their name.

Reminder: As of PDK 1.14.1, use of the PDK with Ruby versions prior to 2.4.0 is now deprecated and a warning will be issued. PDK 1.16.0 is still fully functional back to Ruby 2.1.9 however we are projecting a PDK 2.0.0 release in early 2020 which will eliminate support for Ruby < 2.4.0.

You can review the full release notes at: https://puppet.com/docs/pdk/1.x/release_notes_pdk.html#release-notes-pdk-x.16

To install or upgrade to this new version, use your platform's package manager (see https://puppet.com/docs/pdk/1.x/pdk_install.html) or download the packages directly for Windows, macOS, and Linux platforms at https://puppet.com/download-puppet-development-kit.

Thanks!


Re: PDK 1.16.0 now available

Jesse Scott
 

On macOS, there was a permissions issue in the PDK 1.16.0 packages (released as PDK 1.16.0.1) which prevented most PDK commands from executing.

PDK 1.16.0.2, a new release that addresses the permissions issue, is now available. This release contains no other changes.

We're sorry for the inconvenience of the broken release and we have added additional package acceptance tests to catch this issue in the future.


On Thu, Feb 6, 2020 at 11:12 AM Puppet Product Updates <puppet-product-updates@...> wrote:
Hello!

The Puppet Developer Experience team is pleased to announce the latest release of the Puppet Development Kit (PDK), version 1.16.0.

Highlights from the 1.16.0 release include:

 - Added a new "use_litmus" setting for auto-generated Travis CI configurations to make it easier to adopt Puppet Litmus in your module CI pipelines.
- PDK will now correctly place new files based on the root of your module even if you invoke `pdk new` from within a subdirectory of your module.
- To ensure that modules are compatible with all Puppet Masters regardless of their locale, `pdk module build` will now reject files that contain non-ASCII characters in their name.

Reminder: As of PDK 1.14.1, use of the PDK with Ruby versions prior to 2.4.0 is now deprecated and a warning will be issued. PDK 1.16.0 is still fully functional back to Ruby 2.1.9 however we are projecting a PDK 2.0.0 release in early 2020 which will eliminate support for Ruby < 2.4.0.

You can review the full release notes at: https://puppet.com/docs/pdk/1.x/release_notes_pdk.html#release-notes-pdk-x.16

To install or upgrade to this new version, use your platform's package manager (see https://puppet.com/docs/pdk/1.x/pdk_install.html) or download the packages directly for Windows, macOS, and Linux platforms at https://puppet.com/download-puppet-development-kit.

Thanks!


PDK 1.16.0 now available

Jesse Scott
 

Hello!

The Puppet Developer Experience team is pleased to announce the latest release of the Puppet Development Kit (PDK), version 1.16.0.

Highlights from the 1.16.0 release include:

 - Added a new "use_litmus" setting for auto-generated Travis CI configurations to make it easier to adopt Puppet Litmus in your module CI pipelines.
- PDK will now correctly place new files based on the root of your module even if you invoke `pdk new` from within a subdirectory of your module.
- To ensure that modules are compatible with all Puppet Masters regardless of their locale, `pdk module build` will now reject files that contain non-ASCII characters in their name.

Reminder: As of PDK 1.14.1, use of the PDK with Ruby versions prior to 2.4.0 is now deprecated and a warning will be issued. PDK 1.16.0 is still fully functional back to Ruby 2.1.9 however we are projecting a PDK 2.0.0 release in early 2020 which will eliminate support for Ruby < 2.4.0.

You can review the full release notes at: https://puppet.com/docs/pdk/1.x/release_notes_pdk.html#release-notes-pdk-x.16

To install or upgrade to this new version, use your platform's package manager (see https://puppet.com/docs/pdk/1.x/pdk_install.html) or download the packages directly for Windows, macOS, and Linux platforms at https://puppet.com/download-puppet-development-kit.

Thanks!


PDK 1.15.0 now available

Jesse Scott
 

Hello!

The Puppet Developer Experience team is pleased to announce the latest release of the Puppet Development Kit (PDK), version 1.15.0.

**Please see the end of this email for some important notes about PDK and the recent releases of Bundler 2.1.0 and Rubygems 3.1.1.**

Highlights from the 1.15.0 release include:

 - The target of the `pdk convert --template-url` option is no longer required to be a Git repository. Further, if the target of `--template-url` is a Git working tree, the state of the files on disk will be used as-is. This should greatly simplify the testing of template changes locally.
 - You can now run `pdk convert --default-template` to switch a module back to the default template.
 - The PDK and Bolt PowerShell modules can now co-exist peacefully. (This is partially resolved by this PDK release and should be fully resolved with the next Bolt release.)
 - We've added an experimental `pdk release` subcommand to help automate the module release process. (Read more at https://puppet.com/docs/pdk/1.x/pdk_reference.html#pdk-release-command and please give us your feedback on this functionality!)
 - PDK packages are now available for Fedora 31. (And no longer available for Fedora 28 or 29.)

Reminder: As of PDK 1.14.1, use of the PDK with Ruby versions prior to 2.4.0 is now deprecated and a warning will be issued. PDK 1.15.0 is still fully functional back to Ruby 2.1.9 however we are projecting a PDK 2.0.0 release in early 2020 which will eliminate support for Ruby < 2.4.0.

You can review the full release notes at: https://puppet.com/docs/pdk/1.x/release_notes_pdk.html#release-notes-pdk-x.15

To install or upgrade to this new version, use your platform's package manager (see https://puppet.com/docs/pdk/1.x/pdk_install.html) or download the packages directly for Windows, macOS, and Linux platforms at https://puppet.com/download-puppet-development-kit.

Thanks!


PDK and Bundler/Rubygems Updates:

This release was packaged shortly before the recent release of Bundler 2.1.0, so it does not include fixes for the various new deprecation warnings that are issued by Bundler 2.1.0. If you are using one of our packaged PDK releases, your invocations of PDK should be unaffected by the new Bundler release. For gem installation users, we recommend you stay on Bundler 2.0.2 for the time being. The Bundler compatability issues will be resolved in a future PDK release.

A related release of Rubygems 3.1.1 (which vendors Bundler 2.1.0) has also been causing issues with PDK-templated Travis and Appveyor CI configurations. Specifically the PDK-templated CI configurations include a `gem update --system` step which attempts to update Rubygems and is now hanging due to Rubygems prompting for interactive confirmation. A workaround for this issue has been merged into the PDK default templates. To adopt these changes immediately, you can run:

pdk convert --template-url=https://github.com/puppetlabs/pdk-templates.git --template-ref=master

on any impacted modules. We strongly recommend you update to the latest PDK and run `pdk update` on your modules before running that command, otherwise you may encounter a large number of unrelated changes to your module.


PDK 1.14.1 now available

Jesse Scott
 

Hello!

The Puppet Developer Experience team is pleased to announce the latest release of the Puppet Development Kit (PDK), version 1.14.1.

This is a minor version release (.z release) that fixes a number of small bugs and issues, including:

 - `pdk test unit --verbose` will now switch RSpec's output format to "documentation" as was originally intended.
- When `pdk console` is used with the `--puppet-dev` flag, PDK will now correctly fetch the latest commits from the upstream puppet source repo.
- PDK is now compatible with a broader range of versions of the "minitar" gem which should unlock the use of PDK with Puppet Litmus on additional platforms (including Windows!)
- Speaking of Windows, PDK now reads command output in binary mode, preserving the line endings used on Windows. Additionally, environment variables on Windows are now accessed with the internal Windows kernel32 methods, preserving non-ASCII values.

Also of note: As of PDK 1.14.1, use of the PDK with Ruby versions prior to 2.4.0 is now deprecated and a warning will be issued. PDK 1.14.1 is still fully functional back to Ruby 2.1.9 however we are projecting a PDK 2.0.0 release in early 2020 which will eliminate support for Ruby < 2.4.0.

You can review the full release notes at: https://puppet.com/docs/pdk/1.x/release_notes_pdk.html#release-notes-pdk-x.14.1

To install or upgrade to this new version, use your platform's package manager (see https://puppet.com/docs/pdk/1.x/pdk_install.html) or download the packages directly for Windows, macOS, and Linux platforms at https://puppet.com/download-puppet-development-kit.

Thanks!


PDK 1.14.0 now available

Jesse Scott
 

Hello!

The Puppet Developer Experience team is pleased to announce the latest release of the Puppet Development Kit (PDK), version 1.14.0.

A few highlights from this release:

 - `pdk convert` has gained a new `--add-tests` flag which will automatically scaffold out missing unit tests for existing classes and defined types when you convert a module.
- `pdk test unit` now runs in an interactive mode by default, meaning you can use tools like Pry to debug your tests without any `pdk bundle` gymnastics.
- An experimental `pdk console` command has been added which launches an interactive REPL powered by puppet-debugger.
- The experimental `pdk new unit_test` command added in PDK 1.13.0 has been finalized as `pdk new test --unit`. This command is now fully documented.

You can review the full release notes at: https://puppet.com/docs/pdk/1.x/release_notes_pdk.html#release-notes-pdk-x.14

To install or upgrade to this new version, use your platform's package manager (see https://puppet.com/docs/pdk/1.x/pdk_install.html) or download the packages directly for Windows, macOS, and Linux platforms at https://puppet.com/download-puppet-development-kit.

Thanks!


PDK 1.13.0 now available

Jesse Scott
 

Hello!

The Puppet Developer Experience team is pleased to announce the latest release of the Puppet Development Kit (PDK), version 1.13.0.

A few highlights from this release:

 - `pdk convert` will now create missing templated files that were previously only created when generating a new module (e.g. README.md)
- A new `pdk config get` command has been added which lets you inspect the both user-level and module-level configuration values. This is an incremental step in rolling out a robust configuration subsystem for PDK over the course of several releases.
- An experimental `pdk new unit_test` command has been added which allows you to generate basic unit test scaffolding for existing resources


To install or upgrade to this new version, use your platform's package manager (see https://puppet.com/docs/pdk/1.x/pdk_install.html) or download the packages directly for Windows, macOS, and Linux platforms at https://puppet.com/download-puppet-development-kit.

Thanks!


New Ruby Facter RFC

Bogdan Irimie
 

Hello

We value the Puppet community and strive to make it seamlessly for all of you to contribute to open source Puppet projects. With this goal in mind, we propose to rewrite Facter in Ruby and to streamline the interaction with you! Attached is a link to the RFC, feel free to comment directly on the document.

https://docs.google.com/document/d/1u4SDoZUK3AXlgbmhOWgU8zR2RZHAHDxRZ9l-znFKWoY/edit?usp=sharing

Best regards,
Bogdan Irimie


chrony module

wattersm@...
 

Hello,

I am interested in migrating the puppet-chrony module to voxpupuli.  The original project has been unmaintained for a few years and I would like to see this module maintained better.

https://github.com/ringingliberty/puppet-chrony/issues/6

As you can see this issue has been open since 2016.  What would I need to do to get this module set up under voxpupuli?


PDK 1.12.0 now available

Jesse Scott
 

Hello!

The Puppet Developer Experience team is pleased to announce the latest release of the Puppet Development Kit (PDK), version 1.12.0.

A few highlights from this release:

 - PDK will now validate the syntax of Embedded Puppet (.epp) files
 - An experimental `pdk new transport` command has been added
 - The process of installing, upgrading, and uninstalling the PDK package on Windows is now dramatically faster (Somebody buy Glenn Sarti a beverage!)
 - Commands invoked through the `pdk bundle` subcommand can now be interacted with

We have also added packages for RHEL 8, Fedora 30, and Debian 10 with this release.


To install or upgrade to this new version, use your platform's package manager (see https://puppet.com/docs/pdk/1.x/pdk_install.html) or download the packages directly for Windows, macOS, and Linux platforms at https://puppet.com/download-puppet-development-kit.

Thanks!


Re: voxpupuli/puppet-confluence question

 

Hi Scott,
I assume just nobody tried it yet. The module has a couple of tests. Did
you try version 6.15.7? You could also try to add acceptance tests to
prove it works / fails.

Cheers, Tim

On 18.07.19 17:39, Seidl, Scott wrote:
I've been reviewing your code/readme's/issues on voxpupuli/puppet-confluence, and have a question that doesn't seem to be answered... it's a simple one so I hope you can take a minute out of your day to respond. All examples/code have Confluence version 5.7.1... is there a reason for that? Will this code support version 6.15.7?

Scott Seidl
Middleware Tech Lead
Schneider
(920) 592-2163
www.schneider.com<http://www.schneider.com/>;
Mail Stop Code: US.GRB.01.03.11

The information contained in this email message may be privileged, confidential and protected from disclosure, and no waiver of any privilege is intended. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender and delete all copies.





Re: New Forge API Endpoints

 

Hi Nik,
sorry for the late reply. I cannot speak for the whole group, but I'm
not aware of anybody of us that has the resources at the moment to patch
blacksmith. Especially since it's currently not broken. Are you able to
provide a pull request? We're happy to review it!

Cheers, Tim

On 15.05.19 23:56, nik.anderson@puppet.com wrote:
[Edited Message Follows]
[Reason: Made the formatting a little less awful]

Hello,

The Forge team is getting ready to announce new API endpoints in a blog post (draft below), and we wanted to give you all a heads up beforehand. In short, we've added public endpoints for module management, and authentication through API keys.

We're planning to add support to the puppet_forge gem for the new endpoints in the future. Does it seem like a possibility for the Blacksmith gem to be updated to use the new API key auth? Anything we can do to help with that?

Thanks!

Nik Anderson

Software Engineer

Pronouns: he / his

nik.anderson@puppet.com

Puppet ( https://puppet.com ). The shortest path to better software.

DRAFT: New Forge API Endpoints for Automating Module Management

Fully automating the lifecycle of your Puppet module - it's the stuff dreams are made of. Ok, maybe not so much for the general public, but if you're a module developer, this is an exciting prospect! That's why we're pleased to announce a new collection of Forge API endpoints that allow for complete programmatic module management. What does that mean? It's now possible to log in to your Forge account, create an API key, and use that key to publish, delete, or deprecate any of your modules directly through the Forge API.

## Current publishing options Taking a step or two back, we know there are a lot of module developers out there using [Blacksmith]( https://github.com/voxpupuli/puppet-blacksmith ) to publish their modules, so you may be wondering how the new endpoints are an improvement. Blacksmith is a great tool that the Puppet community built in part to fill the gaps in the Forge API. However, some of the prior limitations in the API meant that the publishing flow of the Blacksmith implementation is somewhat less than ideal. For example, since we hadn't yet implemented authentication through API keys, the Blacksmith workflow involves passing a Forge username and password in plain text. This made automated publishing possible, but we’re excited to be able to provide a more standard authentication flow.

## Beyond just publishing Initially we only set out to create a publish endpoint within our v3 namespace for the Forge API. After thinking about the work this would entail and the community needs, we decided it was important to add endpoints for other essential module management tasks as well, namely deletion and deprecation. We ended up adding the following endpoints:
* `POST /v3/releases`
* `DELETE /v3/releases/<release-slug>`
* `DELETE /v3/modules/<module-slug>`
* `PATCH /v3/modules/<module-slug>` (used for module deprecation)

With that, it's possible to automate the entire module lifecycle. Here's an outline of what those steps might look like using `curl`:

To publish a new module release using curl, you can run this command:
~~~ $ curl -D- --request 'POST' ' https://forgeapi.puppet.com/v3/releases ' \ -F file=@nkanderson-testmodule-0. 1.0.tar.gz \ -H 'Authorization: Bearer <REPLACE WITH YOUR API KEY>' ~~~

And to mark a module release as deleted:
~~~ $ curl -D- --request DELETE \ ' https://forgeapi.puppet.com/v3/releases/nkanderson-testmodule-0.1.0?reason=buggy+release ' \ -H 'Authorization: Bearer <REPLACE WITH YOUR API KEY>' ~~~

Deleting the entire module will mark all individual releases as deleted, effectively removing it from the Forge web interface:
~~~ $ curl -D- --request DELETE \ ' https://forgeapi.puppet.com/v3/modules/nkanderson-testmodule?reason=buggy+module ' \ -H 'Authorization: Bearer <REPLACE WITH YOUR API KEY>' ~~~

To mark a module as deprecated, use the PATCH method. Note that json data is required to specify the deprecate action. Optional parameters include the reason for deprecation and the slug for a replacement module.
~~~ $ curl -D- --request PATCH ' https://forgeapi.puppet.com/v3/modules/nkanderson-testmodule ' \ -d '{"action": "deprecate", "params": {"reason": "No longer maintained", "replacement_slug": "puppetlabs-mysql"} }' \ -H 'Content-Type: application/json' -H 'Authorization: Bearer <REPLACE WITH YOUR API KEY>' ~~~

## Bonus: Updated docs! Once we got into the documentation phase for these new endpoints, we realized our Forge API docs could use a little love. So another improvement we made along the way was to update our docs framework. Beyond just a fresh coat of paint, the new docs are clearer and easier to navigate, with added descriptions for a handful of parameters that hadn’t previously surfaced from implementation to the docs. (Screenshot of New Forge API docs)

Want to try it out? Log in to your Forge account, navigate to your user profile page (hint: click your name in the upper right), and on that page you'll see an option to create a new key. Once you've created a key, you're all set to hit the ground running with automating your module management.




voxpupuli/puppet-confluence question

Seidl, Scott <SeidlS@...>
 

I’ve been reviewing your code/readme’s/issues on voxpupuli/puppet-confluence, and have a question that doesn’t seem to be answered… it’s a simple one so I hope you can take a minute out of your day to respond.  All examples/code have Confluence version 5.7.1… is there a reason for that?  Will this code support version 6.15.7?

 

Scott Seidl

Middleware Tech Lead

Schneider

(920) 592-2163

www.schneider.com

Mail Stop Code:  US.GRB.01.03.11

 

The information contained in this email message may be privileged, confidential and protected from disclosure, and no waiver of any privilege is intended. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender and delete all copies.

 


PDK 1.11.1 now available

Jesse Scott
 

Hello!

We’re pleased to announce the latest release of Puppet Development Kit (PDK), version 1.11.1.

This release contains fixes for two bugs that were impacting the usage of PDK in Continuous Integration (CI) environments such as Travis CI:
  • PDK will now use environment variables to recognize common CI environments and always treat those environments as "noninteractive" which will bypass (among other things) the recently added analytics opt-out prompt.
  • The analytics opt-out prompt will now always be skipped if the PDK_DISABLE_ANALYTICS environment variable is set.
To learn more about these issues and the fixes implemented, please see the PDK release notes: https://puppet.com/docs/pdk/1.x/release_notes_pdk.html#release-notes-pdk-x.11.1

To upgrade to this new version, download it for Windows, macOS, and Linux platforms at https://puppet.com/download-puppet-development-kit. For Yum or Apt-based Linux users, you can install PDK via the Puppet Linux repos or using yum or apt on the Linux command line. macOS users can also install and upgrade via Homebrew: https://github.com/puppetlabs/homebrew-puppet#pdk

Thanks!


PDK 1.11.0 now available

Jesse Scott
 

Hello Vox Pupuli!

We’re pleased to announce the latest release of Puppet Development Kit (PDK), version 1.11.0.

This release contains a variety of incremental improvements and bug fixes. You can review the full release notes at: https://puppet.com/docs/pdk/1.x/release_notes_pdk.html#release-notes-pdk-x.11

Additionally, PDK now gathers anonymous data about your PDK usage. This data helps us understand how you use PDK and how we can improve it. You can opt out of data collection at any time. For details about what data is collected, how your data is anonymized, and how to opt out, see the documentation for PDK analytics: https://puppet.com/docs/pdk/1.x/pdk_install.html#pdk-analytics

To upgrade to this new version, download it for Windows, macOS, and Linux platforms at https://puppet.com/download-puppet-development-kit. For Yum or Apt-based Linux users, you can install PDK via the Puppet Linux repos or using yum or apt on the Linux command line.

Thanks!


Adding analytics to PDK

Jesse Scott
 

TL;DR: We are adding anonymous usage reporting to PDK in the next release, very similar to what is in Bolt. PDK will ask you on first use if you want to opt-out. You can also opt-out later by editing a config file or setting an environment variable.

Hello everyone,

The PDK team would like to let you know that the next version of PDK will include some basic usage reporting/analytics code to help us measure overall adoption and better understand the ways users are interacting with PDK.

All reporting is anonymous and we redact anything that could be considered sensitive before it leaves your system.

Furthermore, to help everyone better understand the shape and scale of the Puppet content developer community it is our intent to make aggregate usage data available on a public dashboard in the future.

Below is a draft of the updated PDK documentation that describes what data is collected and reported as well as how to opt out. One thing that the draft documentation currently does not reflect is that you can also opt out by setting the environment variable "PDK_DISABLE_ANALYTICS=true".

Please let us know if you have any questions or concerns.

Thanks!

-- The PDK Team


PDK data collection

PDK collects usage data to help us understand how it's being used and how we can improve it. You can opt out of data collection at any time; see the section below about opting out.

We collect these values for every analytics event:
  • A random non-identifying user ID. This ID is shared with Bolt analytics, if you've installed Bolt and enabled analytics.
  • PDK installation method (package or gem).
  • Version of PDK.
  • Operating system and version.
For every successful command line invocation of PDK, we collect:
  • The PDK command executed, such as "pdk new module" or "pdk validate".
  • Anonymised command options and arguments.
  • The version of Ruby used to execute the PDK command.
  • The output formats for the command.
  • PDK_* environment variables and their values, if set.
  • Whether a template repository, if used, is default or custom — we do not record the path to the template repo itself.
  • If the default template repo is used, we collect events for each file rendered, recording whether the file is unmanaged, deleted, customized, or default. For customized files, we do not record what changed, only that it was changed in the .sync.yml file.
Note: All arguments and non-Boolean option values, except --puppet-version and --pe-version are redacted in our collected data.

Invalid commands are submitted as a distinct analytics events with the arguments and option values redacted.

To see the data PDK collects, add --debug to a command.

We test the analytics calls strictly to ensure that no unexpected data is accidentally passed in.

Opting out of PDK data collection

The first time you run PDK, it asks you if you want to opt out of data collection. To opt out of data collection after that, edit the analytics.yml file, setting the disabled key to true.

The location of this configuration file depends on your operating system and configuration:
  • For most *nix systems, where the $XDG_CONFIG_HOME variable is set: ${XDG_CONFIG_HOME}/puppet/analytics.yml
  • For most macOS systems, where the $XDG_CONFIG_HOME variable is not set: ~/.config/puppet/analytics.yml
  • For Windows: %LOCALAPPDATA%/puppet/analytics.yml


Re: Deprecate voxpupuli/nscd in favor of ghoneycutt/nscd

Steve Traylen
 

The VP module is probably more modern currently. It's mostly missing support for other OSes and exposing every variable . Adding those things is probably similar to modernising GC module. 
Have been planning to add the missing stuff to VP one . Was stuck behind a MR that has been there for ages.

I say we just merge the functionality of the two modules. Nothing is wrong in either module.

On Tue, 11 Jun 2019, 19:10 James Powis, <powisj@...> wrote:
My largest concern comes from deprecating a community supported module in favor of a single individual supported module. Humans die easily, groups die less easily.

Also Vox really needs some level of guidelines for how a module leaves Vox and / or is deprecated in favor of something else.

Thanks,

James R. Powis


On Mon, Jun 10, 2019 at 1:05 PM Garrett Honeycutt <gh@...> wrote:
Hello,

Would like to propose deprecating voxpupuli/nscd[1] in favor of
ghoneycutt/nscd[2].

My version has all the functionality present in VP's version and is
feature complete to the documentation on all supported platforms. VP's
supports EL 6 and 7 and mine supports EL 5-7, Amazon Linux, Debian 6,
Solaris 10, Suse 10-12, 15, OpenSuse 13 and Ubuntu 12. They are both
under the Apache v2 license.

What my module is missing is strong data types, puppet-strings
documentation (though every parameter is already documented), hiera data
in module and acceptance tests. It does have comprehensive spec tests
and is widely used in production.

[1] - https://github.com/voxpupuli/puppet-nscd
[2] - https://github.com/ghoneycutt/puppet-module-nscd

Best regards,
-g

--
Garrett Honeycutt
@learnpuppet
Puppet Training with LearnPuppet.com
Mobile: +1.206.414.8658



61 - 80 of 371