From a1207eb0a4fe58d90fea257f026ed00b80ee33d4 Mon Sep 17 00:00:00 2001 From: Michael Derynck Date: Thu, 23 May 2024 10:35:13 -0600 Subject: [PATCH] Fix missing filtering term type 1 when editing jinja route template (#4357) # What this PR does When editing a jinja route template the filtering_term_type was not being provided so it was being validated as regex instead. This adds the missing flag so that the route will use the correct validation. The reason this was not being hit in the past is most jinja templates were still passing regex validation. ## Which issue(s) this PR closes Closes #4259 ## Checklist - [ ] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes. --- grafana-plugin/src/pages/integration/Integration.tsx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/grafana-plugin/src/pages/integration/Integration.tsx b/grafana-plugin/src/pages/integration/Integration.tsx index 64c9c587..6f2ec9b6 100644 --- a/grafana-plugin/src/pages/integration/Integration.tsx +++ b/grafana-plugin/src/pages/integration/Integration.tsx @@ -186,7 +186,7 @@ class _IntegrationPage extends React.Component this.onUpdateRoutesCallback(values, channelFilterId, 1)} template={selectedTemplate} templateBody={ selectedTemplate?.name === 'route_template'