Skip to content

Commit

Permalink
feat: Add Debricked Scan->SSC action (closes #41)
Browse files Browse the repository at this point in the history
  • Loading branch information
rsenden committed May 31, 2024
1 parent b02d1d7 commit b669ca0
Show file tree
Hide file tree
Showing 4 changed files with 75 additions and 0 deletions.
1 change: 1 addition & 0 deletions doc-resources/action-ssc-debricked-scan.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
# TODO
11 changes: 11 additions & 0 deletions doc-resources/templates/ssc-debricked-scan/README.template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# fortify/github-action/ssc-debricked-scan@{{var:action-major-version}}

{{include:p.marketing-intro.md}}

{{include:action-ssc-debricked-scan.md}}

{{include:h2.support.md}}

---

*[This document was auto-generated; do not edit by hand](https://github.com/fortify/shared-doc-resources/blob/main/USAGE.md)*
37 changes: 37 additions & 0 deletions ssc-debricked-scan/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
# fortify/github-action/ssc-debricked-scan@v1


<!-- START-INCLUDE:p.marketing-intro.md -->

[Fortify Application Security](https://www.microfocus.com/en-us/solutions/application-security) provides your team with solutions to empower [DevSecOps](https://www.microfocus.com/en-us/cyberres/use-cases/devsecops) practices, enable [cloud transformation](https://www.microfocus.com/en-us/cyberres/use-cases/cloud-transformation), and secure your [software supply chain](https://www.microfocus.com/en-us/cyberres/use-cases/securing-the-software-supply-chain). As the sole Code Security solution with over two decades of expertise and acknowledged as a market leader by all major analysts, Fortify delivers the most adaptable, precise, and scalable AppSec platform available, supporting the breadth of tech you use and integrated into your preferred toolchain. We firmly believe that your great code [demands great security](https://www.microfocus.com/cyberres/application-security/developer-security), and with Fortify, go beyond 'check the box' security to achieve that.

<!-- END-INCLUDE:p.marketing-intro.md -->



<!-- START-INCLUDE:action-ssc-debricked-scan.md -->

# TODO

<!-- END-INCLUDE:action-ssc-debricked-scan.md -->



<!-- START-INCLUDE:h2.support.md -->

## Support

The only warranties for products and services of Open Text and its affiliates and licensors (“Open Text”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.

The software is provided "as is" and is not supported through the regular OpenText Support channels. Support requests may be submitted through the [GitHub Issues](https://github.com/fortify/github-action/issues) page for this repository. A (free) GitHub account is required to submit new issues or to comment on existing issues.

Support requests created through the GitHub Issues page may include bug reports, enhancement requests and general usage questions. Please avoid creating duplicate issues by checking whether there is any existing issue, either open or closed, that already addresses your question, bug or enhancement request. If an issue already exists, please add a comment to provide additional details if applicable.

Support requests on the GitHub Issues page are handled on a best-effort basis; there is no guaranteed response time, no guarantee that reported bugs will be fixed, and no guarantee that enhancement requests will be implemented. If you require dedicated support for this and other Fortify software, please consider purchasing OpenText Fortify Professional Services. OpenText Fortify Professional Services can assist with general usage questions, integration of the software into your processes, and implementing customizations, bug fixes, and feature requests (subject to feasibility analysis). Please contact your OpenText Sales representative or fill in the [Professional Services Contact Form](https://www.microfocus.com/en-us/cyberres/contact/professional-services) to obtain more information on pricing and the services that OpenText Fortify Professional Services can provide.

<!-- END-INCLUDE:h2.support.md -->


---

*[This document was auto-generated; do not edit by hand](https://github.com/fortify/shared-doc-resources/blob/main/USAGE.md)*
26 changes: 26 additions & 0 deletions ssc-debricked-scan/action.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
name: 'Perform SAST scan'
description: 'Perform a SAST scan on ScanCentral SAST'
author: 'Fortify'
runs:
using: composite
steps:
- uses: fortify/github-action/[email protected]
with:
export-path: false
fcli: action-default
debricked-cli: action-default
- uses: fortify/github-action/internal/[email protected]
- run: ${DEBRICKED_CLI_CMD} scan
shell: bash
- if: always()
run: ${FCLI_CMD} ssc artifact import-debricked --av "${SSC_APPVERSION}"" --repository "${{ github.repository }}"" --branch "${{ github.head_ref || github.ref_name }}" -t ${{ env.DEBRICKED_TOKEN }} --store debricked_scan
shell: bash
- if: env.DO_WAIT == 'true' || env.DO_EXPORT == 'true'
run: |
${FCLI_CMD} ssc artifact wait-for ::debricked_scan::
shell: bash

branding:
icon: 'shield'
color: 'blue'

0 comments on commit b669ca0

Please sign in to comment.