[irfn]

Description

Export GitHub Actions workflow traces to Scout via OpenTelemetry using a workflow_run trigger, requiring no changes to existing workflows.

Required secrets to configure in repo Settings > Secrets and variables > Actions:

Secret	Source
SCOUT_OTLP_ENDPOINT	Provided during Scout onboarding
SCOUT_TENANT	Your Scout tenant identifier
SCOUT_CLIENT_ID	OAuth2 client ID from Scout
SCOUT_CLIENT_SECRET	OAuth2 client secret from Scout

GITHUB_TOKEN is auto-provided by GitHub Actions.

Checklist

• I have updated the PR title to match CDKTN's style guide
• I have run the linter on my code locally
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation if applicable
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works if applicable
• New and existing unit tests pass locally with my changes

[irfn]

@so0k i am not sure which of these scopes would the Github action fit in?

Unknown scope "github actions" found in pull request title "chore(github actions): Adding base14 Scout CI/CD observability workflow to instrument all the github actions.". Scope must match one of: lib, cli, hcl2json, hcl2cdk, provider-generator, tests, examples, readme, docs, release, deps.

[jsteinich]

@so0k i am not sure which of these scopes would the Github action fit in?

Unknown scope "github actions" found in pull request title "chore(github actions): Adding base14 Scout CI/CD observability workflow to instrument all the github actions.". Scope must match one of: lib, cli, hcl2json, hcl2cdk, provider-generator, tests, examples, readme, docs, release, deps.

It's possible to just skip the scope. All that does is group things in the changelog. We could also add a new scope.

[irfn]

It's possible to just skip the scope. All that does is group things in the changelog. We could also add a new scope.

I would suggest adding gha for github actions related work. WDYT @jsteinich

[so0k]

It's possible to just skip the scope. All that does is group things in the changelog. We could also add a new scope.

I would suggest adding gha for github actions related work. WDYT @jsteinich

yeah, do i need to push that to main? or if you include it in this PR it will pass the linter?

[irfn]

@so0k please check now, the Lint PR is passing now.

[so0k]

also, the Secrets have been added to the this repo:

# github_actions_secret.cdk-terrain_repo_secret-scout-client-id_3AA86A63 will be created
  + resource "github_actions_secret" "cdk-terrain_repo_secret-scout-client-id_3AA86A63" {
      + created_at       = (known after apply)
      + destroy_on_drift = true
      + id               = (known after apply)
      + plaintext_value  = (sensitive value)
      + repository       = "cdk-terrain"
      + secret_name      = "SCOUT_CLIENT_ID"
      + updated_at       = (known after apply)
    }

  # github_actions_secret.cdk-terrain_repo_secret-scout-client-secret_F594B5DF will be created
  + resource "github_actions_secret" "cdk-terrain_repo_secret-scout-client-secret_F594B5DF" {
      + created_at       = (known after apply)
      + destroy_on_drift = true
      + id               = (known after apply)
      + plaintext_value  = (sensitive value)
      + repository       = "cdk-terrain"
      + secret_name      = "SCOUT_CLIENT_SECRET"
      + updated_at       = (known after apply)
    }

  # github_actions_secret.cdk-terrain_repo_secret-scout-otlp-endpoint_104811C1 will be created
  + resource "github_actions_secret" "cdk-terrain_repo_secret-scout-otlp-endpoint_104811C1" {
      + created_at       = (known after apply)
      + destroy_on_drift = true
      + id               = (known after apply)
      + plaintext_value  = (sensitive value)
      + repository       = "cdk-terrain"
      + secret_name      = "SCOUT_OTLP_ENDPOINT"
      + updated_at       = (known after apply)
    }

  # github_actions_secret.cdk-terrain_repo_secret-scout-tenant_31109379 will be created
  + resource "github_actions_secret" "cdk-terrain_repo_secret-scout-tenant_31109379" {
      + created_at       = (known after apply)
      + destroy_on_drift = true
      + id               = (known after apply)
      + plaintext_value  = (sensitive value)
      + repository       = "cdk-terrain"
      + secret_name      = "SCOUT_TENANT"
      + updated_at       = (known after apply)
    }

[irfn]

@so0k i've verified that all the required secrets are setup

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.