-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rework sensu_silenced name handling #1015
Comments
treydock
added a commit
to treydock/sensu-puppet
that referenced
this issue
Nov 16, 2018
treydock
added a commit
to treydock/sensu-puppet
that referenced
this issue
Nov 17, 2018
treydock
added a commit
to treydock/sensu-puppet
that referenced
this issue
Jan 8, 2019
treydock
added a commit
to treydock/sensu-puppet
that referenced
this issue
Jan 8, 2019
treydock
added a commit
to treydock/sensu-puppet
that referenced
this issue
Jan 10, 2019
treydock
added a commit
to treydock/sensu-puppet
that referenced
this issue
Jan 13, 2019
Instead of changing naming it was just documented how the naming works and tests added to validate what is documented. Closing via #1041. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The name passed like this:
Will be replaced in
metadata
withentity:sensu_agent:*
. The name passed during creation isn't used, and based on docs name is a#{subscription}:#{check}
. To avoid confusion and inconsistent behavior the name of asensu_silenced
resource should match the convention that one would see when looking at things through sensuctl.The text was updated successfully, but these errors were encountered: