[IDP-592] Add owner field to Agent Integrations (Part 4/4: S-Z) #21017
+44
−0
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.
Add
owner
field set toagent-integrations
to manifest.json files for Agent Integrations (Part 4/4: S-Z) (44 integrations):silk, silverstripe_cms, singlestore, slurm, snowflake, solr, sonarqube, sonatype_nexus, spark, squid, ssh_check, statsd, strimzi, supabase, supervisord, suricata, systemd, teamcity, tekton, temporal, tenable, teradata, terraform, tibco_ems, tls, tokumx, tomcat, torchserve, traefik_mesh, traffic_server, twemproxy, twistlock, varnish, vault, velero, vertica, vllm, voltdb, watchguard_firebox, weaviate, weblogic, yarn, zeek, zk
Note: These integrations are our best guesses for the Agent Integrations team. If you don't own these integrations, or if you also own other integrations that should be included, please let us know.
This provides clear ownership tracking for these agent integrations as part of the initiative to add owner fields to all integration manifest.json files.
Please note: You may encounter validation errors such as
Error in manifests: {'owner': ['Unknown field']}
during CI checks. These can be safely ignored as we're working to update the manifest schema validation in parallel. We're seeking team approval on ownership assignments while addressing the technical validation separately.For reviewer: Please confirm:
agent-integrations
the correct Datadog team slug in org 2 for tracking ownership?team
tag? We believe it should be "Agent Integrations" - could you confirm this is the correct workday team name?Thank you for your review!