Remove default username for sensu #214
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In some cases we need a passwordless sensu dashboard for different reasons, for example if we would like to manage the Auth using Nginx + Google_Auth_proxy[1]. Adding the default sensu user on the provider would mean that we have to authenticate everytime which doesn't make much sense. [1] https://github.com/bitly/google_auth_proxy
jamtur01
added a commit
that referenced
this pull request
Aug 8, 2014
Remove default username for sensu
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some cases we need a passwordless sensu dashboard for different reasons, for example if we would like to manage the Auth using Nginx + Google_Auth_proxy[1].
Adding the default sensu user on the provider would mean that we have to authenticate everytime which doesn't make much sense. Also managing default values on the type limits the usage of the $sensu::dashboard_user which might be intended to manage our configurations. Having two entry points is difficult to handle imho.
closes #205
[1] https://github.com/bitly/google_auth_proxy