The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
Puppet Module Tool should interact with the forge using SSL
|Assignee:||Ken Barber||% Done:|
|Affected Puppet version:||Branch:||https://github.com/kbarber/puppet/tree/ticket/3.0rc/14598-interact_with_the_forge_using_ssl|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.
Puppet Module Tool should interact with the forge using SSL.
As we are start to create more interactions requiring a higher level of security, this would be a step in the right direction.
#3 Updated by Ken Barber over 1 year ago
- Branch changed from https://github.com/puppetlabs/puppet/pull/804 to https://github.com/kbarber/puppet/tree/ticket/master/14598-interact_with_the_forge_using_ssl
So the current acceptance tests fail due to lack of a ca_path or ca_file setting. Have sent a mail out to puppet-dev to see what solution people would prefer for this.
#5 Updated by Ken Barber over 1 year ago
- Target version changed from Waldorf to 3.0.0
- Branch changed from https://github.com/kbarber/puppet/tree/ticket/master/14598-interact_with_the_forge_using_ssl to https://github.com/kbarber/puppet/tree/ticket/3.0rc/14598-interact_with_the_forge_using_ssl
Kelsey has offered to test and review this for a 3.0.0 target, so the new branch rebased from 3.0rc is here: