You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the method for passing a network config matches all others, however this adds to the instances array.
This should not map to the same, rather only a single entry can work for monitoring the network state of an instance.
As reported in DataDog#98, it is possible to abuse attributes in a manner that
the netowkr check will contain multiple instances.
This change will raise the problem to the user as a WARN, but still
enable them to render an incorrect file, as we don't know which
attribute invocation they would want.
A simpler workaround is to use override_attributes where necessary, as
the default_attributes may be getting appended to the exisiting default
array, as definced in the attributes/network.rb file.
FixesDataDog#98
n1koo
pushed a commit
to Shopify/chef-datadog
that referenced
this issue
Oct 20, 2014
Currently, the method for passing a
network
config matches all others, however this adds to the instances array.This should not map to the same, rather only a single entry can work for monitoring the network state of an instance.
a role:
Along with the default attributes file
network.rb
will result in the following yaml:The text was updated successfully, but these errors were encountered: