module-ownership-example.yml

# Module Ownership Configuration
# 
# This file maps module identifiers to their owners/teams.
# The 'identifier' field supports wildcards (* and ?) to match multiple modules.
# The 'owner' field is used for grouping modules in reports.
# The 'internal' field (optional) marks modules as internal, enabling filtering in reports.
#
# Important: Module names in report.json remain unchanged (e.g., "ProfisPartnerCore").
# The owner field is added for grouping/categorization purposes.
#
# Note: The main app module is automatically tagged with owner='App' and internal=true
# based on the IPA's Info.plist. You can override this by explicitly configuring it here.
#
# Example entries:

# Match all modules with "Core" in the name and assign to "Core" owner
# Mark as internal to enable filtering
- identifier: "*Core*"
  owner: Core
  internal: true

# Match specific module
- identifier: "Authentication"
  owner: Security

# Match all network-related modules (external)
- identifier: "Network*"
  owner: Infrastructure
  internal: false