…ther than String

Bitbucket webhook secret

Acceptance tests run requests in parallel commented

modulesync 2.4.0

…o bitbucket-webhook-secret

…-secret

…ne on master

Adding BitBucket Server secret support.

The module already does not support Gentoo and the portage code is no
longer maintained.

Remove Gentoo/portage related code as is it not supported.

* The PROXY.md file is not shown on the forge
* The `doc/` directory is used by puppet-strings
* The information in the file is outdated as the bug in rubygems has been fixed a long time ago

Unify docs

Allow puppetlabs/inifile 3.x

The deploy and deploy_module methods are already running in a detached
forked process, and therefore running the command in the background is
redundant. Additionally, by running the command in the background, we lose
the ability to capture the exit code, and assume it always succeeds.

Running the command in-band additionally allows us to correctly call the
slack and rocketchat notifiers, which previously were silenced.

When generate_types is called before the slack/rocketchat notifiers,
it causes the chat notifications to be in reverse order, since the
generate_types command will also send its own notifications.

By calling generate_types after the chat notifiers, the messages appear
in the correct order in chat.

Since the chat notifiers are the only thing that actually uses this value
(because the deploy and deploy_module methods are run in detached forked
processes), the actual value doesn't really matter.

There are check in the notify_* methods that check for either a 200 or
500 value, so values passed in should be one of these two values.

Keeping the chat status codes at 202 results in broken chat messages,
since the color and attachment are not defined.

Since the deploy and deploy_module methods are now detached forked
processes, their return codes and output are no longer returned
automatically to the payload and module endpoints, and we must manually
define a return value for them.

Since the work has been sent off to an out-of-band process at the time
the webhook call returns, a 202 response is acceptable.

Since the generate_types method defines an :environment key rather
than a :module or :branch, the target value is not defined. We fix
that by looking for an :environment key and setting target.

Additionally, the phrasing is not valid for generating types, so
the phrasing has been updated to better reflect what actually happened.

stdlib 6.0.0 is due to be released soon.
This module has already dropped support for puppet 4 and/or doesn't
use the updated stdlib `merge` function.

See
https://github.com/puppetlabs/puppetlabs-stdlib/blob/217068f97edd2396ce37ac8c1bd7e23da621d6be/CHANGELOG.md#supported-release-600

Allow `puppetlabs/stdlib` 6.x

Convert mocha to rspec-mocks

I have no idea, why this worked at #484.

modulesync 2.7.0 and drop puppet 4

Add support for proxy settings

Webhook improvements

Remove support for providers yum, zypper

The configuration file for the webhook config writes values that
begin with colons (:) as symbols rather than strings, to allow
for calculated values.

Since slack emoji names follow the pattern of `:name:`, they are
written as symbols instead of strings, and the resulting config
file breaks the webhook service.

This change simply requires slack icons to be entered without the
wrapping colons, and adds them back just before sending to Slack.

Where previously the ocean icon would be written as `:ocean:` in
the webhook_slack_icon parameter, now it would be written as `ocean`.

Wrap slack_icon with colons

Release 7.0.0