Skip to content

Commit

Permalink
SDK v1.31.11 Validate docs (#1621)
Browse files Browse the repository at this point in the history
  • Loading branch information
@content-bot
content-bot authored Sep 9, 2024
1 parent e7de34c commit 640354b
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/concepts/demisto-sdk-validate.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -238,7 +238,7 @@ Validate will run all the validations with error codes "BA100", "BA101", "BA102"
| IN121 | Validate that fetch integration has the required params in the right format. | Malformed or missing parameters can lead to errors or incomplete data. For more details, see https://xsoar.pan.dev/docs/integrations/fetching-incidents | |
| IN122 | Validate that all existing params are in the right format for feed params. | Malformed or missing parameters can lead to errors or incomplete data. For more details, see https://xsoar.pan.dev/docs/integrations/feeds | |
| IN123 | Checks if integration display name is versioned correctly, e.g.: ends with v<number>. | Integration display names should end with 'v<number>' for version clarity and consistency. | Yes |
| IN124 | Validate that a param is not hidden if it can not be hidden. | Hiding these parameters can lead to confusion and may prevent the integration from working as expected. Only the following parameters may be hidden: {'feedIncremental', 'longRunning', 'feedReputation'} | Yes |
| IN124 | Validate that a param is not hidden if it can not be hidden. | Hiding these parameters can lead to confusion and may prevent the integration from working as expected. Only the following parameters may be hidden: {'longRunning', 'feedIncremental', 'feedReputation'} | Yes |
| IN125 | Validate that the max_fetch param has a defaultvalue | To maintain optimal load in the platform, the maximal number of incidents per fetch is limited. For more details, see https://xsoar.pan.dev/docs/integrations/fetching-incidents#fetch-limit | Yes |
| IN126 | Validate that a fetch integration is not missing the first_fetch & max_fetch params. | 'first_fetch' and 'max_fetch' parameters in fetch integrations ensure correct incident retrieval. Their absence or incorrect format can lead to errors or inconsistencies. For more details, see https://xsoar.pan.dev/docs/integrations/fetching-incidents#first-run | |
| IN127 | Validate that a deprecated integration display name ends with (Deprecated). | Deprecated integrations should end with (Deprecated) in the display name to clearly indicate their status. This prevents inadvertent use of unsupported integrations. For more details, see https://xsoar.pan.dev/docs/reference/articles/deprecation-process-and-hidden-packs#how-to-deprecate-an-integration | Yes |
Expand Down Expand Up @@ -346,7 +346,7 @@ Validate will run all the validations with error codes "BA100", "BA101", "BA102"
| RM108 | This validation verifies that images in the readme and description files are relative and stored in doc_files. | Using relative references to files in the repo folder enhances security by reducing reliance on external links, minimizing the risk of link manipulation or redirection attacks. | |
| RM109 | Validates if there is a readme file for the content item. | Ensure that the content item contains additional information about use-cases, inputs, and outputs. | |
| RM113 | Validate that non of the readme lines contains the disallowed copyright section keywords. | Content in the Cortex marketplace is licensed under the MIT license. | |
| RM114 | Validate README images used in README exist. | Missing images are not shown in rendered markdown | |
| RM114 | Validate that images placed under doc_files folder and used in README exist. | Missing images are not shown in rendered markdown | |
## `RN`: Release Note
| Code | Description | Rationale | Autofixable |
|--------|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|---------------|
Expand Down

0 comments on commit 640354b

Please sign in to comment.