|
| 1 | +# [Required] |
| 2 | +# Possible values for the Catalog item that can be deployed on a DataMiner System: |
| 3 | +# - Automation: If the Catalog item is a general-purpose DataMiner Automation script. |
| 4 | +# - Ad Hoc Data Source: If the Catalog item is a DataMiner Automation script designed for an ad hoc data source integration. |
| 5 | +# - ChatOps Extension: If the Catalog item is a DataMiner Automation script designed as a ChatOps extension. |
| 6 | +# - Connector: If the Catalog item is a DataMiner XML connector. |
| 7 | +# - Custom Solution: If the Catalog item is a DataMiner Solution. |
| 8 | +# - Data Query: If the Catalog item is a GQI data query. |
| 9 | +# - Data Transformer: Includes a data transformer that enables you to modify data using a GQI data query before making it available to users in low-code apps or dashboards. |
| 10 | +# - Dashboard: If the Catalog item is a DataMiner dashboard. |
| 11 | +# - DevTool: If the Catalog item is a DevTool. |
| 12 | +# - Learning & Sample: If the Catalog item is a sample. |
| 13 | +# - Product Solution: If the Catalog item is a DataMiner Solution that is an out-of-the-box solution for a specific product. |
| 14 | +# - Scripted Connector: If the Catalog item is a DataMiner scripted connector. |
| 15 | +# - Standard Solution: If the Catalog item is a DataMiner Solution that is an out-of-the-box solution for a specific use case or application. |
| 16 | +# - System Health: If the Catalog item is intended to monitor the health of a system. |
| 17 | +# - User-Defined API: If the Catalog item is a DataMiner Automation script designed as a user-defined API. |
| 18 | +# - Visual Overview: If the Catalog item is a Microsoft Visio design. |
| 19 | +# |
| 20 | +type: Custom Solution |
| 21 | +# [Required] |
| 22 | +# The ID of the Catalog item. |
| 23 | +# All registered versions for the same ID are shown together in the Catalog. |
| 24 | +# This ID cannot be changed. |
| 25 | +# If the ID is not filled in, the registration will fail with HTTP status code 500. |
| 26 | +# If the ID is filled in but does not exist yet, a new Catalog item will be registered with this ID. |
| 27 | +# If the ID is filled in but does exist, properties of the item will be overwritten. |
| 28 | +# Must be a valid GUID. |
| 29 | +id: 4c5d14ab-9cec-4c0b-8b58-af379fdb4123 |
| 30 | +# [Required] |
| 31 | +# The human-friendly name of the Catalog item. |
| 32 | +# Can be changed at any time. |
| 33 | +# Max length: 100 characters. |
| 34 | +# Cannot contain newlines. |
| 35 | +# Cannot contain leading or trailing whitespace characters. |
| 36 | +title: $SCRIPTNAME$ |
| 37 | +# [Optional] |
| 38 | +# General information about the Catalog item. |
| 39 | +# Max length: 100,000 characters |
| 40 | +short_description: This is a custom solution for DataMiner. |
| 41 | +# [Optional] |
| 42 | +# A valid URL that points to the source code. |
| 43 | +# A valid URL |
| 44 | +# Max length: 2048 characters |
| 45 | +# Note: When Skyline Communications Reusable GitHub workflows are used, this will be automatically filled in. |
| 46 | +source_code_url: |
| 47 | +# [Optional] |
| 48 | +# A valid URL that points to documentation. |
| 49 | +# A valid URL |
| 50 | +# Max length: 2048 characters |
| 51 | +# Note: When Skyline Communications Reusable GitHub workflows are used, this will be automatically filled in. |
| 52 | +documentation_url: |
| 53 | +# [Optional] |
| 54 | +# People who are responsible for this Catalog item. Might be developers, but this is not required. |
| 55 | +# Format: 'name <email> (URL)' |
| 56 | +# The name is required; max 256 characters. |
| 57 | +# The email and URL are optional, and should be in valid email/URL formats. |
| 58 | +owners: |
| 59 | + - name: '$AUTHOR$' |
| 60 | +# [Optional] |
| 61 | +# Tags that allow you to categorize your Catalog items. |
| 62 | +# Max number of tags: 5 |
| 63 | +# Max length: 50 characters. |
| 64 | +# Cannot contain newlines. |
| 65 | +# Cannot contain leading or trailing whitespace characters. |
| 66 | +tags: |
| 67 | + - dataminer |
0 commit comments