Skip to content

chore: klaviyo -- normalize colon spacing in manifest monitors section#23641

Open
guttymora wants to merge 1 commit intomasterfrom
gustavo.mora/klaviyo-manifest-formatting
Open

chore: klaviyo -- normalize colon spacing in manifest monitors section#23641
guttymora wants to merge 1 commit intomasterfrom
gustavo.mora/klaviyo-manifest-formatting

Conversation

@guttymora
Copy link
Copy Markdown
Contributor

What does this PR do?

Normalizes colon spacing in the monitors section of klaviyo/manifest.json so it matches the rest of the file (no space before :), aligning with the formatting used in dashboards and elsewhere in this manifest.

Motivation

Note

Re-trigger APW publish to the staging COBS keyspace.
After talking with IDP, by generating this PR we ensure we trigger APW flow redeploying the manifest content to COBS.

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
  • If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

@dd-octo-sts
Copy link
Copy Markdown
Contributor

dd-octo-sts Bot commented May 8, 2026

⚠️ Recommendation: Add qa/skip-qa label

This PR does not modify any files shipped with the agent.

To help streamline the release process, please consider adding the qa/skip-qa label if these changes do not require QA testing.

@dd-octo-sts
Copy link
Copy Markdown
Contributor

dd-octo-sts Bot commented May 8, 2026

Validation Report

All 20 validations passed.

Show details
Validation Description Status
agent-reqs Verify check versions match the Agent requirements file
ci Validate CI configuration and Codecov settings
codeowners Validate every integration has a CODEOWNERS entry
config Validate default configuration files against spec.yaml
dep Verify dependency pins are consistent and Agent-compatible
http Validate integrations use the HTTP wrapper correctly
imports Validate check imports do not use deprecated modules
integration-style Validate check code style conventions
jmx-metrics Validate JMX metrics definition files and config
labeler Validate PR labeler config matches integration directories
legacy-signature Validate no integration uses the legacy Agent check signature
license-headers Validate Python files have proper license headers
licenses Validate third-party license attribution list
metadata Validate metadata.csv metric definitions
models Validate configuration data models match spec.yaml
openmetrics Validate OpenMetrics integrations disable the metric limit
package Validate Python package metadata and naming
readmes Validate README files have required sections
saved-views Validate saved view JSON file structure and fields
version Validate version consistency between package and changelog

View full run

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.

2 participants