zaproxy / zaproxy/action-api-scan
Artifact with this name already exists
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 77
- Forks
- 24
- Avg merge
- 13h 44m
- Merged PRs (30d)
- 3
Description
Since moving to v0.9 (and upload-artifactv4) I have problem with following error
Error: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
Seems there was some breaking changes here https://github.com/actions/upload-artifact/issues/480
This is how I run action
- name: zap-api-scan
uses: zaproxy/action-api-scan@77dfa9a647bb0f583e39d4df8531634d6ddd8df4 # 0.9.0
with:
token: ${{ secrets.GITHUB_TOKEN }}
docker_name: 'ghcr.io/zaproxy/zaproxy:stable'
format: openapi
target: ./api-oas.json
cmd_options: '-a'
fail_action: false
allow_issue_writing: false
tried to add
artifact_name: zap-report-${{ github.run_id }}-${{ github.run_attempt }}
but did not help. Any idea how to fix that?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the provided GitHub Actions workflow with upload-artifact v4 and trace how the action handles artifact_name. Done means the scan completes without the 409 conflict and produces the expected report artifact with the shown workflow inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100