Sources

Sources are project-level service accounts that let Modulos retrieve operational signals and compliance-relevant context for a project.

Where in Modulos

• Project → Settings → Sources

123

Sources are managed in Project Settings and are shown with their type and mode. UI shown in light mode.

1. 1
   Sources tab

   Project-level sources live in Project Settings.
2. 2
   Add Source

   Add a new integration source to the project.
3. 3
   Type and mode

   Each source is labeled with its type and whether it is pull or push.

Who can do what

Permissions

• Owners and Editors can create, update, and delete sources.
• Reviewers and Auditors can view sources for assurance and audit purposes.

Sources vs connectors

Sources are not the same as Scout connectors:

• Sources are attached to a project and are intended for service-to-service access.
• Connectors are attached to a user and typically use OAuth for user-scoped access.

Sources

Service accounts attached to projects

• Shared across the project
• Used for automation and monitoring
• Designed for least privilege and rotation

Connectors

User accounts connected to users

• Bound to a person
• Used for user-scoped access
• Reflects individual permissions and accountability

Why this matters

Different permission model

Different rotation and lifecycle

Different audit story

Supported source types

Modulos supports multiple source types, but not every source type can power automated tests.

Sources used for automated tests

These sources provide metrics that can be evaluated by tests:

• Prometheus
• Datadog
• Modulos Client: available by default and used for push-style metrics and artifacts

Sources used for project context

These sources are commonly used to support governance work, but they do not currently provide testing metrics:

• GitHub
• Azure

Tests require metrics

Automated tests require a metrics-capable source such as Prometheus, Datadog, or Modulos Client.

Each source has a mode:

• Pull: Modulos connects out to retrieve data
• Push: an external agent or client pushes data into Modulos

How it works

When you create a source, Modulos:

• stores the source configuration at the project level
• tests connectivity before saving
• stores secrets securely and does not expose them back to the UI after creation

123

Add a source by selecting an integration type and entering the required credentials. UI shown in light mode.

1. 1
   Integration type

   Select the system you want to connect to the project.
2. 2
   Configuration fields

   Enter the credentials and settings for the selected integration.
3. 3
   Save

   Modulos validates the connection before saving the source.

Metrics and discovery

Tests run on metrics. In practice, there are two ways to provide them:

• Pull metrics from Prometheus or Datadog by selecting an existing metric name from your monitoring system.
• Push metrics using Modulos Client, where your code logs metric values to Modulos.

Security best practices

Treat sources as production integrations:

• create dedicated service accounts with least privilege
• rotate tokens and secrets regularly
• scope access to only the projects and repositories you need

Related pages

Testing Operating Model

How testing fits into continuous governance

Tests & Schedules

Define conditions and schedules over metrics

Project Settings

Where sources are configured and who can edit them

Scout Connectors

User-level OAuth connectors for Scout