https://github.com/previousnext/zap-orb
CircleCI Orb for OWASP Zap
https://github.com/previousnext/zap-orb
go ops
Last synced: about 1 year ago
JSON representation
CircleCI Orb for OWASP Zap
- Host: GitHub
- URL: https://github.com/previousnext/zap-orb
- Owner: previousnext
- License: mit
- Created: 2023-08-24T01:04:48.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2024-10-11T11:47:54.000Z (over 1 year ago)
- Last Synced: 2025-03-28T10:52:13.497Z (about 1 year ago)
- Topics: go, ops
- Language: Go
- Homepage:
- Size: 244 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# OWASP Zap CircleCI Orb
## Resources
[CircleCI Orb Registry Page](https://circleci.com/orbs/registry/orb/pnx/zap) - The official registry page of this orb for all versions, executors, commands, and jobs described.
[CircleCI Orb Docs](https://circleci.com/docs/2.0/orb-intro/#section=configuration) - Docs for using and creating CircleCI Orbs.
## Known Issues
### Scenario 1
You may get this error when pushing a new PR,
```
The dev version of pnx/zap@dev:alpha has expired. Dev versions of orbs are only valid for 90 days after publishing.
```
If you see this error, you need to publish a dev:alpha version manually. The fix is to run this:
```
circleci orb pack ./src | circleci orb validate -
circleci orb pack ./src | circleci orb publish - pnx/zap@dev:alpha
```
### Scenario 2
If you see this error:
```
Error: AUTHORIZATION_FAILURE
```
You'll need to cycle your tokens by creating a new API token in CircleCI and updating the token.
Instructions for achieving this on a local file system:
```
circleci setup
A CircleCI token is already set. Do you want to change it Yes
CircleCI API Token ----------
API token has been set.
CircleCI Host https://circleci.com
CircleCI host has been set.
Setup complete.
Your configuration has been saved to /home/user/.circleci/cli.yml.
```