[Puppet Users] Re: Forge doesn't work reliably for me

2014-07-02 Thread Jesse Scott
This appears to be a bug with how we report that you already have the 
latest available version for modules that only have a single release. I've 
opened a ticket in our bug tracker which you can follow here:

https://tickets.puppetlabs.com/browse/PUP-2882

If you have any additional information you would like to share related to 
this issue, you can do so on that ticket.


Thanks for the report!

-Jesse


On Tuesday, July 1, 2014 8:04:20 PM UTC-7, Michael Legleux wrote:
>
> I'm also seeing this on:
> https://forge.puppetlabs.com/rismoney/windowsnetwork
>
> On Monday, June 30, 2014 5:24:17 AM UTC-7, Jonathan Gazeley wrote:
>>
>> Recently I have been unable to upgrade some modules (or check for 
>> upgrades) from Puppet Forge using the module tool. 
>>
>> All of my modules were originally installed from the Forge. This problem 
>> only occurs with some modules but it always occurs. 
>>
>> [jg4461@puppet-prod ~]$ sudo puppet module upgrade ghoneycutt-sysklogd 
>> Notice: Preparing to upgrade 'ghoneycutt-sysklogd' ... 
>> Notice: Found 'ghoneycutt-sysklogd' (v1.0.0) in /etc/puppet/modules ... 
>> Notice: Downloading from https://forgeapi.puppetlabs.com ... 
>> Error: Could not upgrade 'ghoneycutt-sysklogd' (v1.0.0 -> latest) 
>>No releases are available from https://forgeapi.puppetlabs.com 
>>  Does 'ghoneycutt-sysklogd' have at least one published release? 
>>
>> Besides ghoneycutt-sysklogd, other modules I am unable to update are 
>> crayfishx-hiera_mysql and mkrakowitzer-stash. 
>>
>> I heard that this problem may be caused by an incorrect Modulefile but 
>> these look OK to me. All three modules exist on the Forge and with the 
>> same name, so I'm not sure what to check next. Any ideas? 
>>
>> Cheers, 
>> Jonathan 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/22637edb-6810-437e-a648-f2bc29d704ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Re: module install fails

2014-11-10 Thread Jesse Scott
Hi André,

Can you re-run the command with the --debug and --trace options? E.g. 
"puppet module install puppetlabs-git --debug --trace"

It's hard to know exactly what's going wrong without the detail those 
options will provide.


-Jesse

On Monday, November 10, 2014 1:26:35 AM UTC-8, André Meyer wrote:
>
> Hello,
>
> Whenever I try to install a module from the puppet forge it fails, for 
> every plugin. Here is an example with the git plugin:
>
> puppet module install puppetlabs-git
> Notice: Preparing to install into /etc/puppet/modules ...
> Notice: Downloading from https://forge.puppetlabs.com ...
> Notice: Installing -- do not interrupt ...
> Error: can't convert nil into String
> Error: Try 'puppet help module install' for usage
>
> My environment:
> Solaris 11 x86
> Puppet Version: 3.4.1 (from the Solaris repos)
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/48fbabfb-95a4-40f4-9c22-88fbb49f804d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Re: module install fails

2014-11-13 Thread Jesse Scott
Hi André,

It looks like it isn't able to find the module's root directory after 
attempting to extract, do you have GNU tar (gtar) installed? I believe that 
is a requirement for the correct functioning of the Puppet module tool on 
Solaris.

-Jesse

On Tuesday, November 11, 2014 12:20:49 AM UTC-8, André Meyer wrote:
>
> Here is the more detailed output:
>
> puppet module install puppetlabs-git --debug --trace
> Notice: Preparing to install into /etc/puppet/modules ...
> Notice: Downloading from https://forge.puppetlabs.com ...
> Notice: Installing -- do not interrupt ...
> Debug: Executing 'tar xzf 
> /var/lib/puppet/puppet-module/cache/https_forge_puppetlabs_com-ed3a0e51b3c1d8d395ffb1d12c849e3f50d35a10/puppetlabs-git-0.2.0.tar.gz
>  
> --no-same-owner -C 
> /var/lib/puppet/puppet-module/cache/tmp-unpacker-f24ee4d5a20c43ed764abf87213b440e73a55b25'
> Debug: Executing 'find 
> /var/lib/puppet/puppet-module/cache/tmp-unpacker-f24ee4d5a20c43ed764abf87213b440e73a55b25
>  
> -type d -exec chmod 755 {} +'
> Debug: Executing 'find 
> /var/lib/puppet/puppet-module/cache/tmp-unpacker-f24ee4d5a20c43ed764abf87213b440e73a55b25
>  
> -type f -exec chmod a-wst {} +'
> Debug: Executing 'chown -R 40:40 
> /var/lib/puppet/puppet-module/cache/tmp-unpacker-f24ee4d5a20c43ed764abf87213b440e73a55b25'
> Error: can't convert nil into String
> /usr/ruby/1.9/lib/ruby/1.9.1/fileutils.rb:1527:in `path'
> /usr/ruby/1.9/lib/ruby/1.9.1/fileutils.rb:1527:in `fu_each_src_dest0'
> /usr/ruby/1.9/lib/ruby/1.9.1/fileutils.rb:1513:in `fu_each_src_dest'
> /usr/ruby/1.9/lib/ruby/1.9.1/fileutils.rb:508:in `mv'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/module_tool/applications/unpacker.rb:48:in
>  
> `extract_module_to_install_dir'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/module_tool/applications/unpacker.rb:18:in
>  
> `run'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/module_tool/applications/installer.rb:60:in
>  
> `block (2 levels) in run'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/module_tool/applications/installer.rb:59:in
>  
> `each'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/module_tool/applications/installer.rb:59:in
>  
> `block in run'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/module_tool/applications/installer.rb:58:in
>  
> `each'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/module_tool/applications/installer.rb:58:in
>  
> `run'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/face/module/install.rb:129:in 
> `block (3 levels) in '
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/interface/action.rb+eval[wrapper]:242:in
>  
> `install'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/application/face_base.rb:229:in
>  
> `main'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/application.rb:372:in 
> `run_command'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/application.rb:364:in 
> `block (2 levels) in run'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/application.rb:470:in 
> `plugin_hook'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/application.rb:364:in 
> `block in run'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/util.rb:468:in 
> `exit_on_fail'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/application.rb:364:in `run'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/util/command_line.rb:137:in 
> `run'
> /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/util/command_line.rb:91:in 
> `execute'
> /usr/sbin/puppet:4:in `'
> Error: Try 'puppet help module install' for usage
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/b97aaf95-5a5f-44bf-9fc7-aa8967b5c55b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Announcement: Puppet Development Kit RFC process and pdk-planning repo

2018-07-11 Thread Jesse Scott
The Puppet Development Kit team is excited to introduce a new RFC-based
open-source planning and design process for the PDK project!

While many changes to the PDK, including bug fixes and documentation
improvements can be implemented and reviewed via the normal GitHub pull
request workflow, some changes are more substantial.

Today, we are committing to putting these more substantial features through
an “in the open” design process prior to implementation work starting. This
new design process is similar to the internal process that we had been
using, with the primary difference being that the whole PDK community will
be able to participate in the new process.

We welcome and encourage feedback from all members of the PDK community,
whether you just started using Puppet and PDK last week or have been
working with Puppet for years. A diversity of perspectives and experience
levels will help make PDK better for everyone.

You can learn more about our new RFC process as well as review recently
introduced proposals from the PDK team in the new “pdk-planning” Github
repository located at https://github.com/puppetlabs/pdk-planning.


Thanks!

-- The PDK Team

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAJEWz_uxYQsYuSuH4S%3DZPqPjsSAynxAeo5zn6zVwXD-jDXK7rw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Adding analytics to PDK

2019-06-25 Thread 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

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAJEWz_t9hCwei3a1%3DNVeO-vztQQfGHzsdyMZZzEA-DG0mAAP-g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Re: PDK 1.16.0 now available

2020-02-11 Thread 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-upda...@puppet.com> 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!
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAJEWz_sKUVMZdeXhzz1g5dbM9NpfXU_%2BqsgB8gjROgS-3J5tcg%40mail.gmail.com.


[Puppet Users] PDK 1.18.0 now available

2020-05-13 Thread Jesse Scott
Hello!

The PDK development team is pleased to announce the latest release of the
Puppet Development Kit (PDK), version 1.18.0.

Highlights from the 1.18.0 release include:

- Added a new, control-repo specific validator for `environment.conf` files.
- Added `pdk set config` and `pdk remove config` subcommands.

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

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!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAJEWz_veycKFQUTHhXJuW567_ST5PhuLoQ4zOzwA3ZFU6c-dgA%40mail.gmail.com.


[Puppet Users] Re: Upcoming Forge IP Address Change

2020-10-26 Thread Jesse Scott
The previously announced DNS changes in this thread have now been made.

As a reminder, the old IP address will still be functional until at least 
November 9th, 2020, however you will have to update your clients to use 
`forgeapi-old.puppet.com` to access the Forge this way.

On Monday, October 12, 2020 at 3:58:00 PM UTC-7 Puppet Product Updates 
wrote:

> On Monday, October 26th, 2020 we will be updating the `forge.puppet.com` 
> and `forgeapi.puppet.com` DNS records (as well as the legacy `
> forge.puppetlabs.com` and `forgeapi.puppetlabs.com` records) to point to 
> a new IPv4 address. This change is being made as part of ongoing work to 
> improve the performance and reliability of the Forge website and API 
> service.
>
> The new IP address is `192.69.65.71`. This address is already functional 
> and you can configure Puppet to use it 
>  via the 
> temporary hostname `forgeapi-new.puppet.com`. We recommend only using 
> this hostname only for testing purposes, please keep your primary 
> configurations pointed to the default hostname.
>
> We realize that some users have to make firewall exceptions so that their 
> clients can access the Puppet Forge which is why we are pre-announcing this 
> change. To help facilitate a smooth transition, the Forge website and API 
> service will continue to be available on the old IP address until at least 
> Monday, November 9th, 2020. 
>
> Users that need to access Forge via the old IP may configure Puppet to 
> use the temporary hostname 
>  `
> forgeapi-old.puppet.com`. Note that this DNS record will be updated to 
> point to the new IP once the old IP is deactivated. Please be sure to make 
> any necessary updates to your firewall configurations before November 9th, 
> 2020.
>
> The Forge API will continue to be available via IPv6 
> 
>  (as 
> well as IPv4 but on a dynamic set of addresses) through the alternate 
> hostname `forgeapi-cdn.puppet.com` with no changes. 
>
> This is the first time in approximately 5 years that we have changed the 
> Forge IP address.
>
> If you have any questions or concerns, please email us at fo...@puppet.com. 
> Thank you.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/35da2c9a-687f-4356-ad3d-eedb875ad2e6n%40googlegroups.com.