Topics

[ANN] Resource API v1.5.0 Release

David Schmitt
 

Hi all,

We're pleased to announce that version 1.5.0 of the Resource API has just been released.

The Resource API provides a simple way to create new native resources in the form of types and providers for Puppet. Using a little bit of ruby, you can finally get rid of that brittle exec, or manage that one API that eluded you until now.

It is provided as a Ruby gem that can be installed on all puppet versions since 4.7, and will be part of puppet6. Support for it has been included as an experimental feature in the Puppet Development Kit (see pdk new provider --help). Use the resource_api module or the puppet 6 nightly packages to deploy it in your infrastructure.

The new release of the Resource API provides the following enhancements:

  • Allow providers to specify a title when there are multiple namevars, to make title patterns more usable. PDK-1150 #115 (da-ar)
  • Sensitive values are now usable like any other puppet4 datatype. PDK-1092 #117 (DavidS)
  • The puppetlabs-resource_api module now "supports" puppet 6. With the integration of Resource API in puppet 6, the module technically is not needed anymore. For backwards compatibility, and to provide a uniform experience across all puppet versions, it is still available, and will work on puppet6 (doing nothing).

The new release also contains the following notable bugfixes:

  • providers that implement simple_get_filter, are now handled correctly. MODULES-7679 #113 (da-ar)
  • default values are not shared across all resource instances anymore. #118 (DavidS)

See the CHANGELOG for a full list of changes.

We encourage all module developers to review the Resource API and use it when creating types and providers. The README gets you going quickly. To see some example code see this simple Philips Hue type or this experimental apt_key provider.

Please let us know of your experiences with the Resource API, either here, on Slack (#forge-modules), or on the github repo.

Thanks, David Schmitt for the Resource API maintainers.

--

Hugo Deprez
 

+


Envoyé depuis ProtonMail mobile



-------- Message d'origine --------
On 13 sept. 2018 à 08:08, David Schmitt < david.schmitt@... > a écrit :

Hi all,

We're pleased to announce that version 1.5.0 of the Resource API has just been released.

The Resource API provides a simple way to create new native resources in the form of types and providers for Puppet. Using a little bit of ruby, you can finally get rid of that brittle exec, or manage that one API that eluded you until now.

It is provided as a Ruby gem that can be installed on all puppet versions since 4.7, and will be part of puppet6. Support for it has been included as an experimental feature in the Puppet Development Kit (see pdk new provider --help). Use the resource_api module or the puppet 6 nightly packages to deploy it in your infrastructure.

The new release of the Resource API provides the following enhancements:

  • Allow providers to specify a title when there are multiple namevars, to make title patterns more usable. PDK-1150 #115 (da-ar)
  • Sensitive values are now usable like any other puppet4 datatype. PDK-1092 #117 (DavidS)
  • The puppetlabs-resource_api module now "supports" puppet 6. With the integration of Resource API in puppet 6, the module technically is not needed anymore. For backwards compatibility, and to provide a uniform experience across all puppet versions, it is still available, and will work on puppet6 (doing nothing).

The new release also contains the following notable bugfixes:

  • providers that implement simple_get_filter, are now handled correctly. MODULES-7679 #113 (da-ar)
  • default values are not shared across all resource instances anymore. #118 (DavidS)

See the CHANGELOG for a full list of changes.

We encourage all module developers to review the Resource API and use it when creating types and providers. The README gets you going quickly. To see some example code see this simple Philips Hue type or this experimental apt_key provider.

Please let us know of your experiences with the Resource API, either here, on Slack (#forge-modules), or on the github repo.

Thanks, David Schmitt for the Resource API maintainers.

--