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.

Sign up for GitHub

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

Jump to bottom

Required Column added #462

Merged
merged 9 commits into from
Sep 20, 2022
Merged

Required Column added #462

Changes from 7 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
333562a
Required column added
souravsk Sep 16, 2022
7dbe4e1
Required column added
souravsk Sep 16, 2022
46ea623
Required column added
souravsk Sep 16, 2022
8cecdc0
Required column added
souravsk Sep 16, 2022
2cada5e
Required column added
souravsk Sep 16, 2022
baaf626
Required column added
souravsk Sep 16, 2022
1aab151
added requested changes
souravsk Sep 17, 2022
13e2528
Made the required changes
souravsk Sep 20, 2022
a905dd1
Made the required changes
souravsk Sep 20, 2022
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
148 changes: 74 additions & 74 deletions docs/actions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,19 +49,19 @@ Follow these steps to set up JIRA integration:
or
* Token: your Personal Access Tokens.

Key | Description | Possible Values
--- | --- | ---
*url* | Jira project url |
*project-key* | The JIRA project key |
*user* | Jira user. Use email for Jira Cloud and UserName for Jira Server/Data Center |
*password* | Optional: User's password. API token can also be used for Cloud Jira instances. |
*token* | Optional: User's Personal Access Token. Used only for Jira Server/Data Center |
*board* | Optional: JIRA board key |
*priority*| Optional: ticket priority, e.g., High |
*assignee*| Optional: comma separated list of users (emails) that will be assigned to ticket, e.g., ["john@yahoo.com"]. To assign a ticket to the Application Owner email address (as defined in Aqua Application Scope, owner email field), specify ["<%application_scope_owner%>"] as the assignee value |
*issuetype*| Optional: issue type, e.g., Bug |
*labels*| Optional: comma separated list of labels that will be assigned to ticket, e.g., ["label1", "label2"]|
*sprint*| Optional: Sprint name, e.g., "3.5 Sprint 8" |
Key | Description | Possible Values | Required
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Key | Description | Possible Values | Required
Key | Description | Supported Values | Required

Or

Suggested change
Key | Description | Possible Values | Required
Key | Description | Values | Required

@simar7 I think the word Possible is a little ambiguos. What do you think?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah your suggestion makes sense

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So which should I select

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd leave it at Values.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay

--------------|----------------------|-----------------|----------
*url* | Jira project url | | YES
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
*url* | Jira project url | | YES
*url* | Jira project url | | Yes

I think it's better use lowercase.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay @krol3
1:- "Yes"
2:- "yes"
which one will be good

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd pick 1.

*project-key* | The JIRA project key | | YES
*user* | Jira user. Use email for Jira Cloud and UserName for Jira Server/Data Center | | YES
*password* | User's password. API token can also be used for Cloud Jira instances. | | NO
*token* | User's Personal Access Token. Used only for Jira Server/Data Center | | NO
*board* | JIRA board key | | NO
*priority* | ticket priority, e.g., High | | NO
*assignee* | comma separated list of users (emails) that will be assigned to ticket, e.g., ["john@yahoo.com"]. To assign a ticket to the Application Owner email address (as defined in Aqua Application Scope, owner email field), specify ["<%application_scope_owner%>"] as the assignee value | | NO
*issuetype* | issue type, e.g., Bug | | NO
*labels* | comma separated list of labels that will be assigned to ticket, e.g., ["label1", "label2"]| | NO
*sprint* | Sprint name, e.g., "3.5 Sprint 8" | | NO

For Jira you can also specify custom fields that will be populated with values.
Use the `unknowns` parameter in cfg.yaml for custom fields.
Expand Down Expand Up @@ -126,15 +126,15 @@ Possible options for getting the field name:
```

## Email
Key | Description | Possible Values
--- | --- | ---
*use-mx* | Whether to send the email as an SMTP server or a client. Specify 'true' if you would like to send email as an smtp server, in this case you don't need to provide user, password, host and port. | true, false
*user* | Optional, if auth supported. User name (usually email address) |
*password* | Optional, if auth supported. Password |
*host* | SMTP host name |
*port* | SMTP port |
*sender* | Sender's email address |
*recipients*| Recipients (array of comma separated emails), e.g. ["john@yahoo.com"]. To send the email to the Application Owner email address (as defined in Aqua Application Scope, owner email field), specify ["<%application_scope_owner%>"] as the recipients value |
Key | Description | Possible Values | Required
-------------|-------------|-----------------|----------
*use-mx* | Whether to send the email as an SMTP server or a client. Specify 'true' if you would like to send email as an smtp server, in this case you don't need to provide user, password, host and port. | true, false |
*user* | if auth supported. User name (usually email address) | | NO
*password* | if auth supported. Password | | NO
*host* | SMTP host name | | YES
*port* | SMTP port | | YES
*sender* | Sender's email address | | YES
*recipients* | Recipients (array of comma separated emails), e.g. ["john@yahoo.com"]. To send the email to the Application Owner email address (as defined in Aqua Application Scope, owner email field), specify ["<%application_scope_owner%>"] as the recipients value | | YES

## Slack
Getting the Slack webhooks [Create a Slack Custom App](https://api.slack.com/messaging/webhooks).
Expand Down Expand Up @@ -169,29 +169,29 @@ You will need to care about an HTTP Event Collector in Splunk Enterprise or Splu
Once you create an HTTP Event Collector you will receive a token. You should provide this token, together with the Splunk HTTP Collector
URL, as part of the cfg.yaml settings.

Key | Description | Possible Values
--- | --- | ---
*token* | The Splunk HTTP event collector token |
*url* | URL to Splunk HTTP event collector (e.g. http://server:8088) |
*size-limit* | Optional. Maximum scan length, in bytes. Default: 10000 | 10000
Key | Description | Possible Values | Required
------------ | ------------------------------------------------------------------ | --------------- | ---------
*token* | The Splunk HTTP event collector token | | YES
*url* | URL to Splunk HTTP event collector (e.g. http://server:8088) | | YES
*size-limit* | Maximum scan length, in bytes. Default: 10000 | 10000 | | NO

## ServiceNow

Key | Description | Possible Values
--- | --- | ---
*user* | ServiceNow user name |
*password* | User API key / password |
*instance* | Name of ServiceNow Instance (usually the XXX at XXX.servicenow.com)|
*board* | ServiceNow board name to open tickets on. Default is "incident" |
Key | Description | Possible Values | Required
---------- | ------------------------------------------------------------------ | --------------- | ---------
*user* | ServiceNow user name | | YES
*password* | User API key / password | | YES
*instance* | Name of ServiceNow Instance (usually the XXX at XXX.servicenow.com)| | YES
*board* | ServiceNow board name to open tickets on. Default is "incident" | |

## Nexus IQ

Key | Description | Possible Values
--- | --- | ---
*user* | Nexus IQ user name |
*password* | Nexus IQ password |
*url* | Url of Nexus IQ server |
*organization-id* | Organization UID like "222de33e8005408a844c12eab952c9b0" |
Key | Description | Possible Values | Required
----------------- | -------------------------------------------------------- | --------------- | --------
*user* | Nexus IQ user name | | YES
*password* | Nexus IQ password | | YES
*url* | Url of Nexus IQ server | | YES
*organization-id* | Organization UID like "222de33e8005408a844c12eab952c9b0" | | YES

## OpsGenie

Expand All @@ -214,24 +214,24 @@ Key | Description | Possible Values

An API key from the `API Key Management` tab will produce an HTTP 403 error. This API Key is valid but cannot create alerts as it lacks necessary permissions.

Key | Required | Description | Possible Values
--- |----------| --- | ---
token | true | an API key from an API integration |
user | false | Display name of the request owner. |
assignee | false | Comma separated list of users that the alert will be routed to send notifications
recipients | false | Comma separated list of users that the alert will become visible to without sending any notification
priority | false | Specify the alert priority. Default is "P3" | "P1" "P2" "P3" "P4" "P5"
tags | false | Comma separated list of the alert tags. |
alias | false | Client-defined identifier of the alert.
entity | false | Entity field of the alert that is generally used to specify which domain alert is related to.
Key | Description | Possible Values | Required
-----------| --------------------------------------- | ----------------|---------
token | an API key from an API integration | | YES
user | Display name of the request owner. | | NO
assignee | Comma separated list of users that the alert will be routed to send notifications | | NO
recipients | Comma separated list of users that the alert will become visible to without sending any notification | | NO
priority | Specify the alert priority. Default is "P3" | "P1" "P2" "P3" "P4" "P5"| NO
tags | Comma separated list of the alert tags. | | NO
alias | Client-defined identifier of the alert. | | NO
entity | Entity field of the alert that is generally used to specify which domain alert is related to. | | NO

## Exec

| Option | Usage |
|-------------|-------------------------------------------------------------------------------------------|
| env | Optional, custom environment variables to be exposed in the shell of the executing script |
| input-file | Required, custom shell script to executed |
| exec-script | Required, inline shell script executed |
Option | Usage | Required
-------------|-------------------------------------------------------------------------------------------|----------
env | custom environment variables to be exposed in the shell of the executing script | NO
input-file | custom shell script to executed | YES
exec-script | inline shell script executed | YES

The Exec Action also internally exposes the `$POSTEE_EVENT` environment variable with the input event that triggered the action. This can be helpful in situations where the event itself contains useful information.

Expand All @@ -243,36 +243,36 @@ Below is an example of using `$POSTEE_EVENT`. It uses the inline exec-script scr

![img_1.png](img/img_1.png)

| Option | Usage |
|----------|-----------------------------------------|
| URL | Required, URL of the remote server |
| Method | Required, e.g., GET, POST |
| Headers | Optional, custom headers to send |
| Timeout | Optional, custom timeout for HTTP call |
| Bodyfile | Optional, input file for HTTP post body |
Option | Usage | Required
----------|-----------------------------------------|----------
URL | URL of the remote server | YES
Method | e.g., GET, POST | YES
Headers | custom headers to send | NO
Timeout | custom timeout for HTTP call | NO
Bodyfile | input file for HTTP post body | NO


## Kubernetes
![img_4.png](img/img_4.png)

| Option | Usage |
|---------------------|---------------------------------------------------------------------------------------------------------------------------------|
| kube-namespace | Required. Kubernetes namespace to use. |
| kube-config-file | Required. Path to .kubeconfig file |
| kube-label-selector | Required, if specifying labels or annotations. |
| kube-actions | Optional, key-value pair of labels and annotations<br/>Labels must be added via "labels" key and Annotations via "annotations". |
Option | Usage | Required
---------------------|---------------------------------------------------------------------------------------------------------------------------------|----------
kube-namespace | Kubernetes namespace to use. | YES
kube-config-file | Path to .kubeconfig file | YES
kube-label-selector | if specifying labels or annotations. | YES
kube-actions | key-value pair of labels and annotations<br/>Labels must be added via "labels" key and Annotations via "annotations". | NO


## Docker
![img_5.png](img/img_5.png)

| Option | Usage |
|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| docker-image-name | Required. Image name of the docker image. |
| docker-cmd | Required. Command to run inside the docker image. |
| docker-env | Optional. Environment variables to set in the container. |
| docker-network | Optional. Connect the action container to the specified network. {e.g. "host"} |
| docker-volume-mounts | Optional*. Volume mounts present inside the container.<br/> * _If you have specified volume mounts, you also need to pass them through into the postee docker container_ |
Option | Usage | Required
----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|----------
docker-image-name | Image name of the docker image. | YES
docker-cmd | Command to run inside the docker image. | YES
docker-env | Environment variables to set in the container. | NO
docker-network | Connect the action container to the specified network. {e.g. "host"} | NO
docker-volume-mounts | *Volume mounts present inside the container.<br/> * _If you have specified volume mounts, you also need to pass them through into the postee docker container_ | NO

!!! note
When running Postee in a Docker container, it is required to mount the Docker socket within the Postee container to be able to spin up Docker Action container instances. This can be done as follows:
Expand Down