Extra string in action output
Open
Nobody has claimed this yet.
upstream
- Dominant language
- JavaScript
- Stars
- 141
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
When the action fails, it add a wrongly formatted message
` - name: Analyze for critical and high CVEs
id: docker-scout-scan
uses: docker/scout-action@v1
with:
command: quickview,cves,recommendations,sbom
image: "${{ inputs.container_image_destination }}:${{ inputs.container_image_destination_tag }}"
sarif-file: docker-scout_scan.sarif
summary: true
exit-code: true
debug: ${{ env.ACTION_STEP_DEBUG == 'true' }}
dockerhub-user: ${{inputs.TOOL_DOCKERHUB_REGISTRY_USER}}
dockerhub-password: ${{inputs.TOOL_DOCKERHUB_REGISTRY_PASS}}
# credentials needed to pull private (base) images
registry-user: ${{inputs.ARTIFACTORY_USER }}
registry-password: ${{inputs.ARTIFACTORY_PASS }}
output: docker-scout_sbom.json
format: spdx
Contributor guide
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
The issue names no source file or test; start by reproducing the failure with the shown Docker Scout GitHub Action configuration and inspect the action's output handling. Compare the logged message with the attached screenshot, then verify that the extra string is gone and the failure output is correctly formatted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, javascript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100