Skip to content
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

fix(datadog) default value for metrics specified twice #8315

Merged
merged 1 commit into from
Feb 21, 2022

Conversation

bungle
Copy link
Member

@bungle bungle commented Jan 20, 2022

Summary

I found out that datadog schema specifies default for metrics in two levels. Once in config field level and second in metrics level. The config field level causes validation errors in schema loading but those errors are ignored by our loader for some reason. Still I think this is a bug and the default should not be there twice.

### Summary

I found out that datadog schema specifies default for metrics in
two levels. Once in config field level and second in metrics level.
The config field level causes validation errors in schema loading
but those errors are ignored by our loader for some reason. Still
I think this is a bug and the default should not be there twice.
@@ -72,7 +72,6 @@ return {
{ protocols = typedefs.protocols },
{ config = {
type = "record",
default = { metrics = DEFAULT_METRICS },
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @kinman who might be affected by the change

@kikito kikito merged commit bba762a into master Feb 21, 2022
@kikito kikito deleted the fix/datadog-schema branch February 21, 2022 18:23
kikito added a commit that referenced this pull request Feb 24, 2022
Several plugins should be bumped because we made changes to them.

On Kong 3.0.0 we will change this so the bundled plugin versions
coincide with Kong version

Bumped because of new features:
* ACME #8114
* Prometheus #8387

Bumped because of new fixes:
* CORS #8401
* oauth2 #8422
* Datadog #8315
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants