[LOGSC-2554] Add bypass annotations for new linter checks #22329
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We’re enabling new linter rules and some integrations are expected to remain non‑compliant. Add permanent bypass annotations so CI stays green and not fail for new PRs.
datadog-agent-integrations-bot
bot
added
integration/consul
integration/docker_daemon
integration/gitlab
integration/gitlab_runner
integration/kafka
integration/mesos_slave
integration/mysql
integration/nagios
integration/nfsstat
integration/postfix
integration/powerdns_recursor
integration/redisdb
integration/squid
integration/statsd
integration/tomcat
integration/zk
integration/nginx_ingress_controller
integration/twistlock
integration/kube_scheduler
integration/harbor
integration/druid
integration/proxysql
integration/azure_active_directory
integration/citrix_hypervisor
integration/traffic_server
integration/boundary
labels
datadog-agent-integrations-bot
bot
added
integration/mimecast
integration/ossec_security
integration/suricata
integration/docusign
integration/ivanti_nzta
integration/ivanti_connect_secure
integration/keda
integration/falco
integration/postmark
integration/cisco_secure_web_appliance
integration/linux_audit_logs
integration/microsoft_sysmon
integration/openvpn
integration/kuma
integration/microsoft_dns
integration/bitwarden
integration/proofpoint_on_demand
integration/beyondtrust_password_safe
integration/symantec_endpoint_protection
integration/wazuh
integration/supply_chain_firewall
integration/forescout
integration/push_security
integration/crowdstrike_fdr
integration/guarddog
integration/brevo
integration/intercom
team/logs-integrations-reviewers
labels
|
This PR does not modify any files shipped with the agent. To help streamline the release process, please consider adding the |
thibaultkrebs
approved these changes
Jan 15, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We’re enabling new linter rules and some integrations are expected to remain non‑compliant. Add permanent bypass annotations so CI stays green and not fail for new PRs.
What does this PR do?
Motivation
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged