Fix issues

splunk · Nov 6, 2024 · 6fe347f · 6fe347f
1 parent c075972
commit 6fe347f
Show file tree

Hide file tree

Showing 29 changed files with 57 additions and 0 deletions.
diff --git a/docs/advanced/custom_mapping.md b/docs/advanced/custom_mapping.md
@@ -1,3 +1,5 @@
+# Custom Mapping
+
 We can use this feature to map each field with meaningful value to display in the table. For example, the category field contains 1, 2, and 4 values, but when those values are displayed, the user might get confused as those values do not signify the meaning of their mapping. To avoid this confusion, the user can map each field with meaningful value as shown in the following example:
 
 If you have fields that are not mandatory but you would like to display them inside table, you can use default value option by providing ```"[[default]]"``` as one of parameters (check example bellow). It is a way to provide some meaningful information for form fields that have not been filled (fill empty cells in table).

diff --git a/docs/advanced/custom_warning.md b/docs/advanced/custom_warning.md
@@ -1,3 +1,5 @@
+# Custom Warning
+
 This feature allows us to pass broarder description on Input and Configuration page displayed under main description.
 
 ### Warning Properties

diff --git a/docs/advanced/dependent_dropdown.md b/docs/advanced/dependent_dropdown.md
@@ -1,3 +1,5 @@
+# Dependent Dropdown
+
 This feature allows dynamic loading options for the `singleSelect` and the `multipleSelect` fields when the options for that field depend on other fields' values. It loads options via an API call to the endpoint mentioned in `endpointUrl` under options when any dependencies field is updated and all required dependencies fields are non-null.
 
 All non-required dependencies fields can be of any type, but all required dependencies fields should only be of single-select type.

diff --git a/docs/advanced/groups_feature.md b/docs/advanced/groups_feature.md
@@ -1,3 +1,5 @@
+# Groups Feature
+
 Using this functionality, the Inputs page form can be divided into distinct sections, each comprising relevant fields. If the `isExpandable` property is set to true in the global configuration file, the group will be in the [collapsible panel](https://splunkui.splunk.com/Packages/react-ui/CollapsiblePanel) type.
 
 The groups will be displayed at the bottom of the form.

diff --git a/docs/advanced/oauth_support.md b/docs/advanced/oauth_support.md
@@ -1,3 +1,5 @@
+# OAuth Support
+
 UCC allows you to add Auth support in the configuration page. In UCC, OAuth2.0 of the Authorization Code Flow `grant` type is used. It only supports the standard parameters specified in [RFCP749](https://www.rfc-editor.org/rfc/rfc6749) for obtaining an authorization code.
 
 Auth can be used inside the entity tag. Use `type: "oauth"` in the entity list and specify the `options` next to the `type: "oauth"`.

diff --git a/docs/advanced/os-dependent_libraries.md b/docs/advanced/os-dependent_libraries.md
@@ -1,3 +1,5 @@
+# OS-dependent libraries
+
 This feature allows you to download and unpack libraries with appropriate binaries for the indicated operating system during the build process.
 To do this, you need to expand the **meta** section in the global configuration with the **os-dependentLibraries** field. This field takes the following attributes:
 

diff --git a/docs/advanced/save_validator.md b/docs/advanced/save_validator.md
@@ -1,3 +1,5 @@
+# Save Validator
+
 This feature allows you to pass a Javascript function as a string to apply customized validation to form data.
 
 By using this approach, you can write custom JavaScript code where you can write your business logic, and validating can return error messages which will be displayed at the top of the form.

diff --git a/docs/advanced/sub_description.md b/docs/advanced/sub_description.md
@@ -1,3 +1,5 @@
+# Sub Description
+
 This feature allows us to pass a broader description on the Input and Configuration pages displayed under main description.
 
 ### Sub Descritpion Properties

diff --git a/docs/alert_actions/adaptive_response.md b/docs/alert_actions/adaptive_response.md
@@ -1,3 +1,5 @@
+# Adaptive Response
+
 The Adaptive Response framework provides a mechanism for running preconfigured actions
 within the Splunk platform or by integrating with external applications.
 These actions can be automatically triggered by correlation search results or manually

diff --git a/docs/alert_actions/alert_scripts.md b/docs/alert_actions/alert_scripts.md
@@ -1,3 +1,5 @@
+# Alert Action Scripts
+
 The following files would be created/ updated in the output folder once you executed the `ucc-gen` command:
 
 | File Location | Content Description | Action |

diff --git a/docs/alert_actions/index.md b/docs/alert_actions/index.md
@@ -2,6 +2,8 @@
 title: Alert Actions
 ---
 
+# Alert Actions
+
 The alert action can help a user to take action on the alerts that have been triggered. The knowledge from Splunk can be sent to an outside service or to pull additional or detailed information related to the trigger details.
 An add-on can have multiple alert actions based on the use cases the add-on provides. You can know more about alert actions from [this documentation](https://docs.splunk.com/Documentation/Splunk/latest/Alert/Aboutalerts).
 

diff --git a/docs/configurations/index.md b/docs/configurations/index.md
@@ -1,3 +1,5 @@
+# Configuration
+
 The `Configuration` tab can have multiple subtabs, for example, a tab for
 account configuration (to configure the account by adding account credentials),
 proxy configuration, and logging level configuration.

diff --git a/docs/configurations/logging.md b/docs/configurations/logging.md
@@ -1,3 +1,5 @@
+# Logging
+
 The logging tab is a predefined component that allows to create the page for changing
 the log level. It is added in the `pages.configuration.tabs` array
 

diff --git a/docs/configurations/proxy.md b/docs/configurations/proxy.md
@@ -1,3 +1,5 @@
+# Proxy
+
 There are fields that need to be specified in order to enable proxy.
 
 ### Fields

diff --git a/docs/custom_ui_extensions/custom_cell.md b/docs/custom_ui_extensions/custom_cell.md
@@ -1,3 +1,5 @@
+# Custom Cell
+
 A Custom Cell is used to update the content of a table cell.
 
 `customCell` attribute will be used in the table header on the inputs and configuration page.

diff --git a/docs/custom_ui_extensions/custom_control.md b/docs/custom_ui_extensions/custom_control.md
@@ -1,3 +1,5 @@
+# Custom Control
+
 The Custom Control feature allows you to display any customised input component in a form. The developer can easily design and render any complex input component with this feature. Modern add-ons frequently require the use of complex input components, and this feature will allow you to use the custom component in the form that is best suited to your needs, without relying on newer releases of UCC for support.
 
 ### Properties

diff --git a/docs/custom_ui_extensions/custom_hook.md b/docs/custom_ui_extensions/custom_hook.md
@@ -1,3 +1,5 @@
+# Custom Hook
+
 Custom Hook is a JavaScript function that allows us to reuse some code throughout the app. It is used to validate form/dialog inputs.
 
 Hook is nothing more than a Javascript event handling on the events `onCreate`, `onChange`, `onRender`, `onSave`, `onSaveSuccess`, `onSaveFail`, and `onEditLoad`.

diff --git a/docs/custom_ui_extensions/custom_menu.md b/docs/custom_ui_extensions/custom_menu.md
@@ -1,3 +1,5 @@
+# Custom Menu
+
 Custom Menu can be created when there is more than one input present on the inputs page.
 
 > This feature is deprecated (will be removed in the next major version) as [`Multilevel Menu`](../inputs/multilevel_menu.md) is now ready to use if more than one input is available.

diff --git a/docs/custom_ui_extensions/custom_row.md b/docs/custom_ui_extensions/custom_row.md
@@ -1,3 +1,5 @@
+# Custom Row
+
 When a row is expanded on the Inputs table or Configuration Table, Custom Row is utilized to incorporate a customized element. By clicking on the icon provided on the left side of each row, the input-specific details are displayed.
 
 ### Properties

diff --git a/docs/custom_ui_extensions/custom_tab.md b/docs/custom_ui_extensions/custom_tab.md
@@ -1,3 +1,5 @@
+# Custom Tab
+
 Custom Tab feature can be used to render any customized UI component in the Configuration tabs. With this feature, you can design and render any complex input with ease. This is an advanced feature and can be leveraged with limitless functionalities. Modern add-ons are receiving complex use cases and this feature will allow you to design the UI perfectly for your case without having to depend on newer releases of UCC for support.
 
 ### Properties

diff --git a/docs/custom_ui_extensions/overview.md b/docs/custom_ui_extensions/overview.md
@@ -1,3 +1,5 @@
+# Overview
+
 The UCC package simplifies the deployment of React applications featuring the Splunk UI by eliminating the need for NodeJS, Yarn, or front-end dependencies installation. The core requirement for deployment is a `globalConfig.json` file. While UCC is designed to support a broad spectrum of use cases, there may be scenarios where the provided API options do not fully meet your needs.
 
 For such instances, UCC has a runtime custom JavaScript loading mechanism. This feature allows for the invocation of specific functionalities at pivotal moments within the application lifecycle, including `onChange` and `onRender` events.

diff --git a/docs/entity/index.md b/docs/entity/index.md
@@ -2,6 +2,8 @@
 title: Entity
 ---
 
+# Entity
+
 ## Entity Properties
 
 | Property                                                         | Type                      | Description                                                                                                                          | Default Value |

diff --git a/docs/entity/modifyFieldsOnValue.md b/docs/entity/modifyFieldsOnValue.md
@@ -1,3 +1,5 @@
+# Modify Fields On Change
+
 This feature allows to specify conditions to modify other fields based on current field value change.
 
 ### Modification Object Properties

diff --git a/docs/entity/validators.md b/docs/entity/validators.md
@@ -1,3 +1,5 @@
+# Validators
+
 Validators define acceptable values for fields.
 
 !!! warning ""

diff --git a/docs/inputs/helper.md b/docs/inputs/helper.md
@@ -2,6 +2,8 @@
 title: Input Helper Module
 ---
 
+# Input Helper Module
+
 Input scripts are regenerated during every build step, in order to keep the arguments
 and options up to date with the global config. To not discard changes made by developers,
 additional helper modules were introduced. Those modules must contain

diff --git a/docs/inputs/index.md b/docs/inputs/index.md
@@ -2,6 +2,8 @@
 title: Inputs
 ---
 
+# Inputs
+
 The input page stores configuration information for data collection. Multiple inputs can be created on the Inputs page.
 
 Developers are required to add services in the global config file to create a new Input. If multiple services are

diff --git a/docs/inputs/multilevel_menu.md b/docs/inputs/multilevel_menu.md
@@ -1,3 +1,5 @@
+# Multi-level Menu
+
 This feature allows us to organize the input services into different categories. As a result, each group/category will have a separate sub-menu that can include numerous types of input services. Inputs services can also belong to multiple groups/categories.
 
 Using the [Custom Hook](../custom_ui_extensions/custom_hook.md), `groupName` can be saved in any form field for a specific inputs service stanza.

diff --git a/docs/inputs/tabs.md b/docs/inputs/tabs.md
@@ -1,3 +1,5 @@
+# Tabs
+
 This feature allows you to separate inputs based on their service name. Use the tabs feature when multiple inputs services are provided in the global configuration file, and you want to display each input service in a separate tab (and table).
 
 The `table` property must be present in the services to use the tabs feature.

diff --git a/mkdocs.yml b/mkdocs.yml
@@ -53,6 +53,7 @@ plugins:
             show_if_no_docstring: true
             filters: ["!^_"]
             show_source: true
+  - autorefs
   - print-site  # should be at the end
 
 nav: