Skip to content
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

Fix typos in docs and release_checklist #1138

Merged
merged 1 commit into from
Feb 7, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/integrations/argocd-integration.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ ___

#### Configure a PreSync hook

The following example of a hook yaml is nearly ready to be added to an existing kubernetes configuration. To complete the configutation, you need to:
The following example of a hook yaml is nearly ready to be added to an existing kubernetes configuration. To complete the configuration, you need to:
- Ensure that the secrets, `known_hosts`, and `ssh_config` volume are relevant for your specific environment.
- Specify a terrascan image.

Expand Down Expand Up @@ -117,7 +117,7 @@ To allow users to check for violations in the web interface, configure the job t
```sh
#!/bin/sh

function send_slack_notificaton {
function send_slack_notification {
channel=$1
username=$2
slack_hook=$3
Expand All @@ -133,7 +133,7 @@ if [ -p /dev/stdin ]; then

cat results.out

send_slack_notificaton $1 $2 $3
send_slack_notification $1 $2 $3

echo "notification exit code: $?"
else
Expand Down
2 changes: 1 addition & 1 deletion docs/usage/command_line_mode.md
Original file line number Diff line number Diff line change
Expand Up @@ -279,7 +279,7 @@ aws_ecr_repository:
|--non-recursive |Use this for non recursive directories and modules scan | By default directory is scanned recursively, if this flag is used then only provided root directory will be scanned|
|--webhook-token string| Token used for sending authenticated requests to the notification webhook | This flag is optional when using the notification webhook|
|--webhook-url | A webhook URL where Terrascan will send JSON scan report and normalized IaC JSON | This overrides any notification webhook URLs configured in config TOML file specified with the `-c` flag|
|--use-terraform-cache |Use this to refer terraform remote modules from terraform init cache rather than downloading | By default remote module will be downloaded in temporary directory. If this flag is set then modules will be refered from terraform init cache if module is not present in terraform init cache it will be downloaded. Directory will be scanned non recurively if this flag is used.(applicable only with terraform IaC provider)|
|--use-terraform-cache |Use this to refer terraform remote modules from terraform init cache rather than downloading | By default remote module will be downloaded in temporary directory. If this flag is set then modules will be referred from terraform init cache if module is not present in terraform init cache it will be downloaded. Directory will be scanned non recursively if this flag is used.(applicable only with terraform IaC provider)|
| --find-vuln | find vulnerabilities | Use this to fetch vulnerabilities identified on the registry for docker images present in IaC the files scanned |
| --repo-url | repository url | This flag can be used to include the repository URL as part of scan results and notifications |
| --repo-ref | repository branch name | This flag can be used to include the repository branch name as part of scan results and notifications |
Expand Down
2 changes: 1 addition & 1 deletion release_checklist.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ Once complete, commit changes and submit a pull request. This should be the last
### Tag the new release with git
Once the changelog PR has been merged, pull the updated code, tag it with the new version number, and push the tag back to the repo:

(again, subsitute v1.5.0 for the appropriate version being released)
(again, substitute v1.5.0 for the appropriate version being released)
```
git pull
git tag v1.5.0
Expand Down