-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Allow specifying artifact name #45
Comments
Sounds good to me! PR much appreciated :) |
I would also like this. Maybe I will work on this sometime. |
@psiinon this issue is resolved with the merging in of this patch to the upstream common library (zaproxy/actions-common#15) and this patch to this repo (#64) |
is this feature available to be used yet? |
Sorry no, #64 hasnt been merged yet - its still WIP, I'll see whats blocking it... |
I'm using a workaround for the moment, if anybody is interested: job-one:
name: Dast report for site one
runs-on: ubuntu-latest
steps:
- name: ZAP Scan
uses: zaproxy/[email protected]
with:
issue_title: site-one
token: ${{ secrets.GITHUB_TOKEN }}
fail_action: false
target: 'https://siteone.com'
format: openapi
- name: Upload report
uses: actions/upload-artifact@v3
with:
name: custom_name.zip
path: zap_scan.zip |
I use a single workflow file to run zap scans on multiple sites. Each site is its own job so they can fail or succeed independently. However, since the artifact name is hard-coded, only the report of the last job to complete is saved.
Would the project be open to a adding support for specifying the artifact name as an option? I'd be glad to submit PRs both here and in actions-common to add this.
The text was updated successfully, but these errors were encountered: