wsandersvco/Veracode Create Teams
Automatically create and manage Veracode teams based on repository configuration
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| github-token | GitHub token with repo access | yes | — |
| veracode-api-id | Veracode API ID for authentication | yes | — |
| veracode-api-key | Veracode API Key for authentication | yes | — |
| repository | GitHub repository name | yes | — |
| owner | GitHub repository owner | yes | — |
| config-repository | Repository containing team mapping configuration | no | veracode |
| config-ref | Branch, tag, or commit SHA for config repository | no | — |
| veracode-team-mapping-yaml | Path to team mapping YAML file | no | team-mapping.yaml |
| veracode-region | Veracode region (US, EU, or FEDERAL) | no | US |
Outputs
| name | description |
|---|---|
| team-id | UUID of the created/updated team |
| team-name | Name of the created/updated team |
| team-legacy-id | Legacy ID of the team in Veracode database |
| action-taken | Action performed: created or updated |
| member-count | Number of members in the team |
| members-added | Number of members successfully added/validated |
| members-skipped | Number of members skipped (not found in Veracode) |
| skipped-users | Comma-separated list of users that were skipped |