Skip to content

Conversation

davidfeng-datadog
Copy link
Contributor

Add owner field set to agent-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:

  1. Is agent-integrations the correct Datadog team slug in org 2 for tracking ownership?
  2. For the display-tile feature flags in SDP, what workday team should we use as the team tag? We believe it should be "Agent Integrations" - could you confirm this is the correct workday team name?

Thank you for your review!

Copy link
Contributor

@estherk15 estherk15 left a comment

Choose a reason for hiding this comment

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

No docs review needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment