airbyte-internal-ops 0.8.0__tar.gz → 0.9.0__tar.gz

{airbyte_internal_ops-0.8.0 → airbyte_internal_ops-0.9.0}/.github/pr-welcome-message.md

@@ -1,15 +1,18 @@
 🎉 **Thanks for opening this pull request!**
 
-Your contribution is appreciated. Here are some helpful commands you can use:
+Your contribution is appreciated.
 
-## Quick Commands
+<details>
+<summary><b>💡 Show Tips and Tricks</b></summary>
+
+### Quick Commands
 - `/autofix` - Auto-format and fix linting issues (ruff format + ruff check --fix)
 - `/lock` - Update the uv.lock file with latest dependencies
 
-## Available Poe Tasks
+### Available Poe Tasks
 You can run any of these tasks using the slash command: `/poe <task-name>`
 
-### Core Tasks
+#### Core Tasks
 - `/poe test` - Run all tests
 - `/poe test-fast` - Run tests with fast exit on first failure
 - `/poe lint` - Check code style and quality  
@@ -17,16 +20,25 @@ You can run any of these tasks using the slash command: `/poe <task-name>`
 - `/poe deps` - Check for unused and missing dependencies
 - `/poe check` - Run format check, linting, dependency check, and tests
 
-### Quick Fixes
+#### Quick Fixes
 - `/poe fix` - Auto-format and fix linting issues
 - `/poe clean` - Clean up build artifacts and cache
 
-### Build & Install
+#### Build & Install
 - `/poe build` - Build the package
 - `/poe install` - Install with development dependencies
 
-### Other Commands
+#### Other Commands
 - `/poe version` - Show package version
 - `/poe pre-commit` - Run pre-commit style checks
 
+</details>
+
+<details>
+<summary><b>📚 Show Repo Guidance</b></summary>
+
 The CI will automatically run tests when you push commits. Happy coding! 🚀
+
+[📝 _Edit this welcome message._](https://github.com/airbytehq/airbyte-ops-mcp/blob/main/.github/pr-welcome-message.md)
+
+</details>

{airbyte_internal_ops-0.8.0 → airbyte_internal_ops-0.9.0}/.github/workflows/semantic-pr-check.yml

@@ -6,7 +6,7 @@ name: Semantic PR Title Validation
 
 on:
   pull_request:
-    types: [opened, edited, ready_for_review]
+    types: [opened, edited, ready_for_review, synchronize]
 
 permissions:
   contents: read

{airbyte_internal_ops-0.8.0 → airbyte_internal_ops-0.9.0}/.github/workflows/sentry-apply-command.yml

@@ -22,6 +22,7 @@ permissions:
   contents: read
   actions: read
   pull-requests: write
+  deployments: write
 
 env:
   STATE_ARTIFACT_NAME: pulumi-sentry-state
@@ -135,6 +136,9 @@ jobs:
           pip install "pulumi>=3.147.0,<4.0.0"
 
       - name: Generate Sentry provider SDK
+        # To avoid failures related to rate limiting:
+        env:
+          GITHUB_TOKEN: ${{ steps.get-app-token.outputs.token }}
         run: |
           pulumi package add terraform-provider jianyuan/sentry 0.14.8
 

{airbyte_internal_ops-0.8.0 → airbyte_internal_ops-0.9.0}/.github/workflows/sentry-preview.yml

@@ -26,6 +26,13 @@ jobs:
       run:
         working-directory: ${{ env.WORKING_DIRECTORY }}
     steps:
+      - name: Authenticate as GitHub App
+        uses: actions/create-github-app-token@v2
+        id: get-app-token
+        with:
+          app-id: ${{ secrets.OCTAVIA_BOT_APP_ID }}
+          private-key: ${{ secrets.OCTAVIA_BOT_PRIVATE_KEY }}
+
       - name: Checkout code
         uses: actions/checkout@v6
 
@@ -42,6 +49,9 @@ jobs:
           pip install "pulumi>=3.147.0,<4.0.0"
 
       - name: Generate Sentry provider SDK
+        # To avoid failures related to rate limiting:
+        env:
+          GITHUB_TOKEN: ${{ steps.get-app-token.outputs.token }}
         run: |
           pulumi package add terraform-provider jianyuan/sentry 0.14.8
 
@@ -121,20 +131,22 @@ jobs:
         id: find-comment
         with:
           issue-number: ${{ github.event.pull_request.number }}
-          comment-author: 'github-actions[bot]'
+          comment-author: 'octavia-bot[bot]'
           body-includes: '<!-- pulumi-preview-comment -->'
+          token: ${{ steps.get-app-token.outputs.token }}
 
       - name: Create or update preview comment
         uses: peter-evans/create-or-update-comment@v5
         with:
+          token: ${{ steps.get-app-token.outputs.token }}
           comment-id: ${{ steps.find-comment.outputs.comment-id }}
           issue-number: ${{ github.event.pull_request.number }}
           edit-mode: replace
           body: |
             <!-- pulumi-preview-comment -->
-            #### Pulumi Preview
+            #### 🔮 Pulumi Preview
 
-            <details><summary>Summary (readable overview)</summary>
+            <details><summary>📋 Summary (readable overview)</summary>
 
             ```
             ${{ steps.preview.outputs.preview_output }}
@@ -142,7 +154,7 @@ jobs:
 
             </details>
 
-            <details><summary>Detailed Diff (property-level changes for audit)</summary>
+            <details><summary>🔍 Detailed Diff (property-level changes for audit)</summary>
 
             ```diff
             ${{ steps.preview_diff.outputs.preview_diff_output }}
@@ -153,4 +165,4 @@ jobs:
             *Pushed by: @${{ github.actor }}, Action: `${{ github.event_name }}`*
 
             ---
-            These changes will be applied when this PR is merged to `main`. Alternatively, you can run `/sentry-apply` to apply these changes now, before merging.
+            ✨ These changes will be applied when this PR is merged to `main`. Alternatively, you can run `/sentry-apply` to apply these changes now, before merging. 🚀

{airbyte_internal_ops-0.8.0 → airbyte_internal_ops-0.9.0}/CONTRIBUTING.md

@@ -94,6 +94,24 @@ gcloud projects add-iam-policy-binding prod-ab-cloud-proj \
 
 Note: `roles/cloudsql.client` is required for the Cloud SQL Python Connector and Cloud SQL Auth Proxy to establish connections. `roles/cloudsql.instanceUser` is typically needed for IAM database authentication; it may be redundant when using username/password authentication (as this codebase does), but some environments may still require it.
 
+#### GCS Metadata Service Bucket Permissions
+
+For tools that interact with the connector metadata service buckets (e.g., `airbyte-ops registry enterprise-stubs sync`), grant read/write access to the appropriate bucket:
+
+```bash
+# Grant read/write access to the dev metadata service bucket
+gcloud storage buckets add-iam-policy-binding gs://dev-airbyte-cloud-connector-metadata-service-2 \
+  --member="serviceAccount:YOUR_SERVICE_ACCOUNT@YOUR_PROJECT.iam.gserviceaccount.com" \
+  --role="roles/storage.objectAdmin"
+
+# Grant read/write access to the prod metadata service bucket (use with caution)
+gcloud storage buckets add-iam-policy-binding gs://prod-airbyte-cloud-connector-metadata-service \
+  --member="serviceAccount:YOUR_SERVICE_ACCOUNT@YOUR_PROJECT.iam.gserviceaccount.com" \
+  --role="roles/storage.objectAdmin"
+```
+
+Note: `roles/storage.objectAdmin` grants read, write, and delete permissions on objects in the bucket. For read-only access, use `roles/storage.objectViewer` instead.
+
 #### Cloud Logging Permissions
 
 For tools that query GCP Cloud Logging (e.g., `lookup_cloud_backend_error`), grant the Logs Viewer role at the project level:

{airbyte_internal_ops-0.8.0 → airbyte_internal_ops-0.9.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: airbyte-internal-ops
-Version: 0.8.0
+Version: 0.9.0
 Summary: MCP and API interfaces that let the agents do the admin work
 Author-email: Aaron Steers <aj@airbyte.io>
 Keywords: admin,airbyte,api,mcp
@@ -32,6 +32,7 @@ Requires-Dist: jinja2<4.0,>=3.1.2
 Requires-Dist: markdown-it-py<3.0,>=2.2.0
 Requires-Dist: pydantic>=2.0.0
 Requires-Dist: pydash<8.0,>=6.0.2
+Requires-Dist: pygithub<3.0,>=2.0
 Requires-Dist: python-dotenv<2.0,>=1.0.0
 Requires-Dist: pyyaml<7.0,>=6.0.0
 Requires-Dist: requests<3.0,>=2.31.0

{airbyte_internal_ops-0.8.0 → airbyte_internal_ops-0.9.0}/infra/sentry/__main__.py

@@ -134,27 +134,28 @@ CONNECTOR_INCIDENTS_OWNERSHIP_RULES = """\
 # Auto assign issue owners in order to forward the alerts to the relevant teams
 # in order to not miss anything, the alerts for api connectors should be set up as [NOT db-connectors]
 
-# python issues should get auto assigned to api connectors team (team-maintain)
-tags.stacktrace_platform:python #team-maintain
-tags.connector_language:python #team-maintain
-tags.source_type:python #team-maintain
-tags.source_type:manifest-only #team-maintain
+# python issues should get auto assigned to api connectors team (team-integrate)
+tags.stacktrace_platform:python #team-integrate
+tags.connector_language:python #team-integrate
+tags.source_type:python #team-integrate
+tags.source_type:manifest-only #team-integrate
 
 # Check failures happening on platform will mark stacktrace_platform as java, thus even if connectors are api connectors they'll be classified as db connectors. Adding the following (incomplete) rules to avoid that scenario.
-tags.connector_repository:airbyte/source-facebook-marketing #team-maintain
-tags.connector_repository:airbyte/source-google-analytics-v4 #team-maintain
-tags.connector_repository:airbyte/source-google-ads #team-maintain
-tags.connector_repository:airbyte/source-bigquery #team-maintain
-tags.connector_repository:airbyte/source-shopify #team-maintain
-tags.connector_repository:airbyte/source-declarative-manifest #team-maintain
+tags.connector_repository:airbyte/source-facebook-marketing #team-integrate
+tags.connector_repository:airbyte/source-google-analytics-v4 #team-integrate
+tags.connector_repository:airbyte/source-google-ads #team-integrate
+tags.connector_repository:airbyte/source-bigquery #team-integrate
+tags.connector_repository:airbyte/source-shopify #team-integrate
+tags.connector_repository:airbyte/source-declarative-manifest #team-integrate
 
 # connector_language is only set on sources
 tags.source_type:java #team-extract
 
-# java and normalization failures should go to either destination or sources
-# order is important here, as python errors in normalization will be routed to dbs
-tags.failure_origin:destination #team-move
-tags.stacktrace_platform:java #team-move"""
+# Source failures should go to team-extract
+tags.failure_origin:source #team-extract
+
+# Destination failures should go to team-move
+tags.failure_origin:destination #team-move"""
 
 # Fingerprint rules for connector-ci project
 CONNECTOR_CI_FINGERPRINTING_RULES = """\
@@ -260,8 +261,11 @@ def define_abctl_project() -> tuple[sentry.Project, OutputVarsMap]:
         filters=sentry.ProjectFiltersArgs(
             error_messages=[
                 "*kong.ParseError: unexpected argument start",
+                "*kong.ParseError: unexpected argument stop",
+                "*kong.ParseError: unknown flag --output",
                 "*values.yaml*no such file or directory*",
                 "*values.yml*no such file or directory*",
+                "*error reading pgdata version file*",
             ],
         ),
         opts=pulumi.ResourceOptions(protect=True),
@@ -761,6 +765,109 @@ def define_connector_incidents_ownership() -> sentry.ProjectOwnership:
     )
 
 
+# =============================================================================
+# CORAL-AGENTS ALERT RULES
+# =============================================================================
+
+
+def define_coral_agents_alert_rules() -> list[sentry.IssueAlert]:
+    """Define alert rules for the coral-agents project.
+
+    Slack-only alerts for the AI agent service. These alerts notify the team
+    when new issues appear or existing issues regress/reappear.
+
+    The High Error Volume alert is a P0-candidate that will trigger PagerDuty
+    once a PagerDuty service is configured for coral-agents. Currently Slack-only.
+
+    Returns:
+        List of IssueAlert resources.
+    """
+    # PagerDuty service ID for coral-agents (to be configured when ownership is determined)
+    # Set to empty string to disable PagerDuty alerts, or set to service ID to enable
+    # To enable: 1) Create PagerDuty service, 2) Link to Sentry, 3) Set service ID here
+    coral_agents_pagerduty_service_id = ""  # TODO: 1) Create PagerDuty service, 2) Link to Sentry, 3) Set service ID here
+
+    # Build actions list - always include Slack, conditionally include PagerDuty
+    high_volume_actions = []
+    if coral_agents_pagerduty_service_id:
+        high_volume_actions.append(
+            sentry.IssueAlertActionsV2Args(
+                pagerduty_notify_service=sentry.IssueAlertActionsV2PagerdutyNotifyServiceArgs(
+                    account="139284",
+                    service=coral_agents_pagerduty_service_id,
+                    severity="critical",
+                ),
+            ),
+        )
+    high_volume_actions.append(
+        sentry.IssueAlertActionsV2Args(
+            slack_notify_service=sentry.IssueAlertActionsV2SlackNotifyServiceArgs(
+                channel="#dev-platform-chatbot-alerts",
+                workspace="139867",
+            ),
+        ),
+    )
+
+    return [
+        # Alert: New or Escalating Issues - catch new bugs early
+        # Triggers on first occurrence, regression, or reappearance of issues
+        sentry.IssueAlert(
+            "alert-coral-agents-new-issues",
+            organization=ORGANIZATION,
+            project=CORAL_AGENTS_PROJECT_ID,
+            name="Coral Agents: New or Escalating Issues",
+            action_match="any",
+            filter_match="all",
+            frequency=5,  # 5 minutes - catch issues quickly
+            environment="prod",
+            conditions_v2s=[
+                sentry.IssueAlertConditionsV2Args(
+                    first_seen_event=sentry.IssueAlertConditionsV2FirstSeenEventArgs(),
+                ),
+                sentry.IssueAlertConditionsV2Args(
+                    regression_event=sentry.IssueAlertConditionsV2RegressionEventArgs(),
+                ),
+                sentry.IssueAlertConditionsV2Args(
+                    reappeared_event=sentry.IssueAlertConditionsV2ReappearedEventArgs(),
+                ),
+            ],
+            filters_v2s=[],  # No filters - alert on all new issues
+            actions_v2s=[
+                sentry.IssueAlertActionsV2Args(
+                    slack_notify_service=sentry.IssueAlertActionsV2SlackNotifyServiceArgs(
+                        channel="#dev-platform-chatbot-alerts",
+                        workspace="139867",
+                    ),
+                ),
+            ],
+        ),
+        # Alert: High Error Volume (P0 candidate) - pages on-call when enabled
+        # Triggers when error volume exceeds threshold, indicating widespread issues
+        # Currently Slack-only; PagerDuty will be enabled when service ID is configured
+        sentry.IssueAlert(
+            "alert-coral-agents-high-volume",
+            organization=ORGANIZATION,
+            project=CORAL_AGENTS_PROJECT_ID,
+            name="Coral Agents: High Error Volume (P0)",
+            action_match="any",
+            filter_match="all",
+            frequency=60,  # Once per hour max to avoid alert fatigue
+            environment="prod",
+            conditions_v2s=[
+                sentry.IssueAlertConditionsV2Args(
+                    event_frequency=sentry.IssueAlertConditionsV2EventFrequencyArgs(
+                        comparison_type="count",
+                        interval="1h",
+                        value=50,  # >=50 events in 1 hour indicates widespread issue
+                    ),
+                ),
+            ],
+            filters_v2s=[],  # No filters - alert on all high-volume issues
+            actions_v2s=high_volume_actions,
+        ),
+    ]
+
+
 # =============================================================================
 # MAIN - Entry point for Pulumi
 # =============================================================================
@@ -785,6 +892,9 @@ def main() -> None:
     # Note: Ownership resource is created for side effects; return value not needed
     define_connector_incidents_ownership()
 
+    # Create alert rules for coral-agents project
+    define_coral_agents_alert_rules()
+
     # Export organization-level outputs
     pulumi.export("organization", ORGANIZATION)
     pulumi.export("alert_rules_url", f"https://{ORGANIZATION}.sentry.io/alerts/rules/")

{airbyte_internal_ops-0.8.0 → airbyte_internal_ops-0.9.0}/pyproject.toml

@@ -29,6 +29,7 @@ dependencies = [
     "markdown-it-py>=2.2.0,<3.0",
     "pydantic>=2.0.0",
     "pydash>=6.0.2,<8.0",
+    "PyGithub>=2.0,<3.0",
     "python-dotenv>=1.0.0,<2.0",
     "pyyaml>=6.0.0,<7.0",
     "requests>=2.31.0,<3.0",