Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: sensu/sensu-puppet
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.19.0
Choose a base ref
...
head repository: sensu/sensu-puppet
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.19.1
Choose a head ref
  • 7 commits
  • 21 files changed
  • 5 contributors

Commits on Jul 9, 2017

  1. check type should notify sensu-enterprise

    David Gwilliam authored and jeffmccune committed Jul 9, 2017
    Configuration menu
    Copy the full SHA
    d4d7908 View commit details
    Browse the repository at this point in the history
  2. (maint) Manage Service[sensu-enterprise] with sensu-server-enterprise VM

    Without this patch the sensu-server-enterprise Vagrant VM is not managing the
    Service[sensu-enterprise] resource.  This is a problem for testing the behavior
    changes made in #720.
    
    This patch addresses the problem by changing the class parameters of the
    provisioning manifest for sensu-server-enterprise.  The credentials for the
    Sensu Enterprise repository are expected to be set in the shell environment
    where `vagrant up` is executed.
    
    For example, the following direnv `.envrc` is sufficient for this project:
    
    ```
    export FACTER_SE_USER='1234567890'
    export FACTER_SE_PASS='Password1'
    ```
    jeffmccune committed Jul 9, 2017
    Configuration menu
    Copy the full SHA
    aa24f84 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    84141f5 View commit details
    Browse the repository at this point in the history
  4. (#495) Notify Service[sensu-enterprise] from Sensu::Check resources

    Without this patch The sensu-enterprise service is not notified automatically
    when `sensu::check` resources are declared.  This patch addresses the problem
    by checking the catalog for the service and automatically adding the notify
    relationship.
    
    resolves #502
    resolves #495
    closes #653
    jeffmccune committed Jul 9, 2017
    Configuration menu
    Copy the full SHA
    ae48859 View commit details
    Browse the repository at this point in the history
  5. Merge pull request #725 from ghoneycutt/388_simplify_class_notifications

    (GH-388) Simplify class notifications
    ghoneycutt authored Jul 9, 2017
    Configuration menu
    Copy the full SHA
    f175f1c View commit details
    Browse the repository at this point in the history

Commits on Jul 10, 2017

  1. Merge pull request #720 from jeffmccune/495_check_should_notify_sensu…

    …-enterprise
    
    (#495) Notify Service[sensu-enterprise] from Sensu::Check resources
    ghoneycutt authored Jul 10, 2017
    Configuration menu
    Copy the full SHA
    339f4a6 View commit details
    Browse the repository at this point in the history
  2. Release v2.19.1

    Fixed bug where sensu::check was not notifying the enterprise service.
    ghoneycutt committed Jul 10, 2017
    Configuration menu
    Copy the full SHA
    bd97d83 View commit details
    Browse the repository at this point in the history
Loading