oteligence-inc/Maestro Instrumentation
Apply Maestro's locked instrumentation config to your JAR build
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| api-key | Maestro API key — use a GitHub Secret, not inline | yes | — |
| project | Maestro project name (e.g. banking-app). Optional if project-id is given. | no | — |
| project-id | Maestro project UID. Wins over `project` when set — use it if the name may be wrong/forgotten. Provide project OR project-id (or both). | no | — |
| service | Service name within the project (e.g. fund-transfer) | yes | — |
| environment | Target env: dev / staging / prod / <custom> | yes | — |
| jars | Glob path to the service JAR (e.g. target/*.jar). v0 expects exactly one match. | yes | — |
| api-url | Override Maestro API base URL (advanced — for testing). Must be https:// | no | https://api.oteligence.com |
| timeout-seconds | Max wait for each Maestro job to complete | no | 300 |
| fail-on-warnings | Fail the step if this run made peer services stale (default: false) | no | false |
| skip-generate-on-inactive | If the tenant subscription is inactive (402), skip extension-JAR generation and continue the pipeline (deploy proceeds WITHOUT a new extension) instead of failing the step. Default false. | no | false |
Outputs
| name | description |
|---|---|
| generated | 'true' when an extension JAR was generated; 'false' when skipped (inactive subscription) |
| extension-dir | Local path to the extracted OTel agent + extension JAR bundle |
| config-path | Local path to the resolved javaagent.config |
| collector-config-path | Local path to the resolved collector config (deploy to your Collector, not the app image) |
| locked-version | The locked version applied (e.g. 22) — use for image labels |
| jar-sha | SHA256 of the uploaded JAR (or cache hit) |
| job-id | Maestro build job ID — for audit / log lookup |