### Complete Sentry Setup Example

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

This comprehensive YAML manifest illustrates the setup of a complete Sentry project, including teams, projects, DSN keys, webhook plugins, and issue alert rules. It defines resources for a 'payments-service' microservice.

```yaml
# Complete Sentry setup for a microservice
---
# Team for the service owners
apiVersion: sentry.justtrack.io/v1alpha1
kind: Team
metadata:
  name: payments-team
spec:
  forProvider:
    name: "Payments Team"
    organization: "my-org"
    slug: "payments-team"
---
# Project for the payments service
apiVersion: sentry.justtrack.io/v1alpha1
kind: Project
metadata:
  name: payments-service
spec:
  forProvider:
    name: "payments-service"
    slug: "payments-service"
    organization: "my-org"
    platform: "python"
    resolveAge: 168  # 1 week
    teamsRefs:
      - name: payments-team
  writeConnectionSecretToRef:
    name: payments-service-conn
    namespace: crossplane-system
---
# DSN key for the service
apiVersion: sentry.justtrack.io/v1alpha1
kind: Key
metadata:
  name: payments-service-key
spec:
  forProvider:
    name: "payments-service-production"
    organization: "my-org"
    projectRef:
      name: "payments-service"
    rateLimitCount: 500
    rateLimitWindow: 60
  writeConnectionSecretToRef:
    name: payments-dsn
    namespace: crossplane-system
---
# Webhook plugin for external notifications
apiVersion: sentry.justtrack.io/v1alpha1
kind: Plugin
metadata:
  name: payments-webhook
spec:
  forProvider:
    organization: "my-org"
    projectRef:
      name: "payments-service"
    plugin: "webhooks"
    config:
      urls: "https://alerts.example.com/sentry/payments"
---
# Alert rule for critical payment errors
apiVersion: sentry.justtrack.io/v1alpha1
kind: IssueAlert
metadata:
  name: payments-critical-alert
spec:
  forProvider:
    name: "Critical Payment Errors"
    organization: "my-org"
    projectRef:
      name: "payments-service"
    environment: "production"
    actionMatch: "any"
    filterMatch: "all"
    frequency: 1  # Alert every minute for critical issues
    conditions:
      - id: "sentry.rules.conditions.first_seen_event.FirstSeenEventCondition"
      - id: "sentry.rules.conditions.event_frequency.EventFrequencyCondition"
        value: "100"
        interval: "1h"
    filters:
      - id: "sentry.rules.filters.level.LevelFilter"
        level: "50"  # CRITICAL level
        match: "gte"
    actions:
      - id: "sentry.rules.actions.notify_event_service.NotifyEventServiceAction"
        service: "webhooks"
```

--------------------------------

### Install Provider Sentry using Up CLI

Source: https://github.com/justtrackio/provider-sentry/blob/main/README.md

Installs the Provider Sentry Crossplane provider using the Up command-line tool. Ensure you replace 'v0.0.0' with the latest release tag.

```bash
up ctp provider install justtrack/provider-sentry:v0.0.0
```

--------------------------------

### Apply and Verify Complete Sentry Setup using Kubectl

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

This section provides bash commands to apply the complete Sentry setup manifest and then wait for the resources to become ready. It also shows how to export the Sentry DSN and list all applied Sentry resources.

```bash
# Apply the complete setup
kubectl apply -f payments-sentry-setup.yaml

# Wait for all resources to be ready
kubectl wait --for=condition=Ready teams.sentry.justtrack.io/payments-team --timeout=60s
kubectl wait --for=condition=Ready projects.sentry.justtrack.io/payments-service --timeout=60s
kubectl wait --for=condition=Ready keys.sentry.justtrack.io/payments-service-key --timeout=60s

# Get the DSN to use in your application
export SENTRY_DSN=$(kubectl get keys.sentry.justtrack.io payments-service-key \
  -o jsonpath='{.status.atProvider.dsnPublic}')
echo "Configure your app with: SENTRY_DSN=$SENTRY_DSN"

# View all Sentry resources
kubectl get teams,projects,keys,issuealerts,plugins --selector=crossplane.io/claim-namespace
```

--------------------------------

### Install Provider Sentry using kubectl

Source: https://github.com/justtrackio/provider-sentry/blob/main/README.md

Installs the Provider Sentry Crossplane provider declaratively using kubectl. This method applies a Provider resource definition to your Kubernetes cluster.

```yaml
cat <<EOF | kubectl apply -f -
apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-sentry
spec:
  package: justtrack/provider-sentry:v0.0.0
EOF
```

--------------------------------

### Run Provider Sentry on Kubernetes Cluster

Source: https://github.com/justtrackio/provider-sentry/blob/main/README.md

Starts the Provider Sentry on a running Kubernetes cluster. This command is used for local development and testing of the provider.

```console
make run
```

--------------------------------

### Apply and Verify Sentry Webhook Plugin using Kubectl

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

These bash commands demonstrate how to apply the Sentry webhook plugin configuration using kubectl and then verify its status. It involves piping the YAML manifest to `kubectl apply -f -` and using `kubectl get plugins.sentry.justtrack.io` to check the resource.

```bash
# Enable webhook plugin for a project
kubectl apply -f - <<EOF
apiVersion: sentry.justtrack.io/v1alpha1
kind: Plugin
metadata:
  name: webhook-integration
  annotations:
    crossplane.io/external-name: webhooks
spec:
  forProvider:
    organization: "my-org"
    projectRef:
      name: "my-api-service"
    plugin: "webhooks"
    config:
      urls: "https://my-webhook.example.com/sentry"
EOF

# Check plugin status
kubectl get plugins.sentry.justtrack.io
# NAME                  SYNCED   READY   EXTERNAL-NAME   AGE
# webhook-integration   True     True    webhooks        30s
```

--------------------------------

### Install Crossplane Provider for Sentry (Bash)

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

Applies the Crossplane Provider for Sentry installation manifest using kubectl. This command streams the YAML definition to kubectl for application.

```bash
kubectl apply -f - <<EOF
apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-sentry
spec:
  package: justtrack/provider-sentry:v0.1.0
EOF

# Verify provider is healthy
kubectl get providers
# NAME              INSTALLED   HEALTHY   PACKAGE                            AGE
# provider-sentry   True        True      justtrack/provider-sentry:v0.1.0   60s
```

--------------------------------

### Install Crossplane Provider for Sentry (YAML)

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

Installs the Crossplane Provider for Sentry using the Crossplane package manager. This involves defining a Provider resource pointing to the package image.

```yaml
apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-sentry
spec:
  package: justtrack/provider-sentry:v0.1.0
```

--------------------------------

### Build Provider Sentry Binary

Source: https://github.com/justtrackio/provider-sentry/blob/main/README.md

Compiles the Provider Sentry project into a standalone binary executable. This is a necessary step before publishing or deploying the provider.

```console
make build
```

--------------------------------

### Publish Provider Sentry Package to Upbound Marketplace

Source: https://github.com/justtrackio/provider-sentry/blob/main/README.md

Pushes the built Provider Sentry package to the Upbound marketplace. Replace 'vX.Y.Z' with the desired version and '$FILENAME' with the path to your package file.

```shell
up xpkg push justtrack/provider-sentry:vX.Y.Z -f $FILENAME
```

--------------------------------

### Run Provider Sentry Code Generation

Source: https://github.com/justtrackio/provider-sentry/blob/main/README.md

Executes the code generation pipeline for the Provider Sentry project. This command is typically used during development to update generated code based on API definitions.

```console
make generate
```

--------------------------------

### Verify Sentry Project Creation

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

Commands to verify the creation and status of a Sentry project managed by Crossplane. It includes checking the project's general status and retrieving detailed information including its internal ID.

```bash
# Verify project creation
kubectl get projects.sentry.justtrack.io

# Check project details including internal ID
kubectl get projects.sentry.justtrack.io my-api-service -o jsonpath='{.status.atProvider}'
```

--------------------------------

### Manage Sentry Team Resource (Bash)

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

Applies a Sentry Team resource definition using kubectl and then checks the status of the created team. It demonstrates creating, applying, and verifying the team resource.

```bash
kubectl apply -f - <<EOF
apiVersion: sentry.justtrack.io/v1alpha1
kind: Team
metadata:
  name: backend-team
  annotations:
    crossplane.io/external-name: backend-team
spec:
  forProvider:
    name: "Backend Team"
    organization: "my-org"
    slug: "backend-team"
  writeConnectionSecretToRef:
    name: backend-team-secret
    namespace: crossplane-system
EOF

# Check team status
kubectl get teams.sentry.justtrack.io
# NAME           SYNCED   READY   EXTERNAL-NAME   AGE
# backend-team   True     True    backend-team    45s

# Get detailed status
kubectl describe teams.sentry.justtrack.io backend-team
# Status:
#   At Provider:
#     Has Access:   true
#     Internal Id:  12345
#     Is Member:    true
#     Slug:         backend-team
```

--------------------------------

### Verify Sentry Key Creation and Retrieve DSN

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

Commands to verify the creation of a Sentry key and retrieve its public DSN. The DSN is essential for configuring applications to send data to Sentry. It also shows how to access the DSN from the Kubernetes secret.

```bash
# Create a key for a project
kubectl apply -f - <<EOF
apiVersion: sentry.justtrack.io/v1alpha1
kind: Key
metadata:
  name: my-api-service-key
spec:
  forProvider:
    name: "my-api-service-key"
    organization: "my-org"
    projectRef:
      name: "my-api-service"
    rateLimitCount: 100
    rateLimitWindow: 60
  writeConnectionSecretToRef:
    name: my-api-service-dsn
    namespace: crossplane-system
EOF

# Check key status
kubectl get keys.sentry.justtrack.io

# Get the DSN from status (for use in your application)
kubectl get keys.sentry.justtrack.io my-api-service-key -o jsonpath='{.status.atProvider.dsnPublic}'

# Access DSN from the connection secret
kubectl get secret my-api-service-dsn -n crossplane-system -o yaml
```

--------------------------------

### Apply and Verify Sentry Provider Configuration (Bash)

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

Applies the Sentry provider configuration defined in a YAML file using kubectl and then verifies the ProviderConfig resource's status.

```bash
kubectl apply -f providerconfig.yaml

# Verify the provider config
kubectl get providerconfigs.sentry.justtrack.io
# NAME      AGE   SECRET-NAME
# default   30s   example-creds
```

--------------------------------

### Authenticate and List Organizations for Upbound

Source: https://github.com/justtrackio/provider-sentry/blob/main/README.md

Lists available organizations within Upbound, typically used before publishing a package. This command requires authentication with the Up CLI.

```shell
up organization list
```

--------------------------------

### Create Sentry Project with Crossplane

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

Defines and creates a Sentry project using the Crossplane Sentry provider. It specifies project details like name, slug, organization, platform, and associated teams. The configuration is applied using kubectl.

```yaml
apiVersion: sentry.justtrack.io/v1alpha1
kind: Project
metadata:
  name: my-api-service
spec:
  forProvider:
    name: "my-api-service"
    slug: "my-api-service"
    organization: "my-org"
    platform: "go"
    resolveAge: 720
    teamsRefs:
      - name: backend-team
  writeConnectionSecretToRef:
    name: my-api-service-secret
    namespace: crossplane-system
```

--------------------------------

### Create Sentry Project Resource (YAML)

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

Defines a Sentry Project custom resource using Kubernetes YAML. This resource configures project details like name, slug, organization, platform, and auto-resolution settings, and associates it with teams.

```yaml
apiVersion: sentry.justtrack.io/v1alpha1
kind: Project
metadata:
  name: my-api-service
  annotations:
    crossplane.io/external-name: my-api-service
spec:
  forProvider:
    name: "my-api-service"
    slug: "my-api-service"
    organization: "my-org"
    platform: "go"
    resolveAge: 720  # Auto-resolve issues after 720 hours
    digestsMaxDelay: 1800
    digestsMinDelay: 300
    teamsRefs:
      - name: backend-team
      - name: platform-team
  writeConnectionSecretToRef:
    name: my-api-service-secret
    namespace: crossplane-system
```

--------------------------------

### Create Sentry Key with Crossplane

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

Defines and creates a Sentry DSN key for a project using the Crossplane Sentry provider. This key is used by applications to send error events to Sentry. It includes rate limiting configurations.

```yaml
apiVersion: sentry.justtrack.io/v1alpha1
kind: Key
metadata:
  name: my-api-service-key
spec:
  forProvider:
    name: "my-api-service-key"
    organization: "my-org"
    projectRef:
      name: "my-api-service"
    rateLimitCount: 100    # Max 100 events
    rateLimitWindow: 60    # Per 60 seconds
  writeConnectionSecretToRef:
    name: my-api-service-dsn
    namespace: crossplane-system
```

--------------------------------

### Configure Sentry Webhook Plugin

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

This snippet shows how to enable and configure the Sentry webhook plugin for a specific project. It requires the organization name, project reference, plugin type ('webhooks'), and the URL for the webhook endpoint.

```yaml
apiVersion: sentry.justtrack.io/v1alpha1
kind: Plugin
metadata:
  name: webhook-integration
  annotations:
    crossplane.io/external-name: webhooks
spec:
  forProvider:
    organization: "my-org"
    projectRef:
      name: "my-api-service"
    plugin: "webhooks"
    config:
      urls: "https://my-webhook.example.com/sentry"
```

--------------------------------

### Verify Sentry Issue Alert Creation

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

Commands to verify the creation and status of a Sentry issue alert managed by Crossplane. It includes checking the alert's general status and retrieving its internal ID.

```bash
# Create an issue alert
kubectl apply -f - <<EOF
apiVersion: sentry.justtrack.io/v1alpha1
kind: IssueAlert
metadata:
  name: critical-errors-alert
spec:
  forProvider:
    name: "Critical Errors Alert"
    organization: "my-org"
    projectRef:
      name: "my-api-service"
    actionMatch: "any"
    filterMatch: "all"
    frequency: 5
    conditions:
      - id: "sentry.rules.conditions.first_seen_event.FirstSeenEventCondition"
    filters:
      - id: "sentry.rules.filters.level.LevelFilter"
        level: "40"
        match: "gte"
    actions:
      - id: "sentry.rules.actions.notify_event_service.NotifyEventServiceAction"
        service: "webhooks"
EOF

# Verify alert creation
kubectl get issuealerts.sentry.justtrack.io

# Get alert internal ID
kubectl get issuealerts.sentry.justtrack.io critical-errors-alert -o jsonpath='{.status.atProvider.internalId}'
```

--------------------------------

### Configure Sentry Provider Credentials (YAML)

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

Sets up authentication for the Sentry provider by creating a Kubernetes Secret containing Sentry API credentials and then configuring a ProviderConfig resource to use this secret.

```yaml
# Create a secret with Sentry credentials
apiVersion: v1
kind: Secret
metadata:
  name: example-creds
  namespace: crossplane-system
type: Opaque
stringData:
  credentials: |
    {
      "base_url": "https://sentry.your-domain.io",
      "token": "your-sentry-auth-token"
    }
---
# Configure the provider with the credentials secret
apiVersion: sentry.justtrack.io/v1beta1
kind: ProviderConfig
metadata:
  name: default
spec:
  credentials:
    source: Secret
    secretRef:
      name: example-creds
      namespace: crossplane-system
      key: credentials
```

--------------------------------

### Create Sentry Team Resource (YAML)

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

Defines a Sentry Team custom resource using Kubernetes YAML. This resource specifies the team's name, organization, and slug, and configures where to write connection secrets.

```yaml
apiVersion: sentry.justtrack.io/v1alpha1
kind: Team
metadata:
  name: backend-team
  annotations:
    crossplane.io/external-name: backend-team
spec:
  forProvider:
    name: "Backend Team"
    organization: "my-org"
    slug: "backend-team"
  writeConnectionSecretToRef:
    name: backend-team-secret
    namespace: crossplane-system
```

--------------------------------

### Configure Sentry Issue Alert with Crossplane

Source: https://context7.com/justtrackio/provider-sentry/llms.txt

Defines and creates an automated alerting rule for Sentry projects using the Crossplane Sentry provider. This configuration includes conditions, filters (e.g., error level), and actions like webhook notifications.

```yaml
apiVersion: sentry.justtrack.io/v1alpha1
kind: IssueAlert
metadata:
  name: critical-errors-alert
spec:
  forProvider:
    name: "Critical Errors Alert"
    organization: "my-org"
    projectRef:
      name: "my-api-service"
    environment: "production"
    actionMatch: "any"      # Trigger on any condition match
    filterMatch: "all"      # All filters must match
    frequency: 5            # Alert at most every 5 minutes
    conditions:
      - id: "sentry.rules.conditions.first_seen_event.FirstSeenEventCondition"
      - id: "sentry.rules.conditions.regression_event.RegressionEventCondition"
    filters:
      - id: "sentry.rules.filters.level.LevelFilter"
        level: "40"         # Error level (40 = ERROR)
        match: "gte"        # Greater than or equal
    actions:
      - id: "sentry.rules.actions.notify_event_service.NotifyEventServiceAction"
        service: "webhooks"
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.