Skip to content

Commit 2ec7a3d

Browse files
Updating documentation
1 parent 9ae0e02 commit 2ec7a3d

File tree

2 files changed

+23
-5
lines changed

2 files changed

+23
-5
lines changed

README.md

+18-4
Original file line numberDiff line numberDiff line change
@@ -21,12 +21,26 @@ The **Skyline.DataMiner.CICD.Tools.GitHubToCatalogYaml** tool automates the crea
2121
| Variable: `CATALOGIDENTIFIER` | `Id` | If not specified in the existing YAML or as a variable, an identifier is generated automatically for each catalog entry. |
2222
| Owners | `Owners` | Customizable, with owner email, name, and URL settings. |
2323

24-
## Auto-Generated Catalog YAML File
24+
## **Auto-Generated Catalog YAML File**
2525

26-
This tool not only extends an existing `catalog.yml` or `manifest.yml` but also generates an `auto-generated-catalog.yml` file in the `.githubtocatalog` directory. This secondary file is essential because:
26+
**WARNING! DO NOT MODIFY THIS FILE.**
2727

28-
1. **Tracking Catalog IDs**: By committing and pushing `auto-generated-catalog.yml`, the tool can create a unique ID on the first run and reuse this ID on future runs. This avoids duplicate catalog records that can occur if new IDs are generated in every workflow run.
29-
2. **Workflow Automation**: The `auto-generated-catalog.yml` is maintained separately to allow other processes to retrieve it as needed without modifying the primary catalog file in each update.
28+
This tool generates an `auto-generated-catalog.yml` file in the `.githubtocatalog` directory, alongside extending any existing `catalog.yml` or `manifest.yml` file. This secondary file is critical for the following reasons:
29+
30+
1. **Tracking Catalog IDs:**
31+
Committing and pushing the `auto-generated-catalog.yml` allows the tool to create a unique Catalog ID on the first run and reuse it for future runs. This prevents duplicate catalog records, which can occur if new IDs are generated with each workflow run.
32+
33+
2. **Workflow Automation:**
34+
The `auto-generated-catalog.yml` is maintained separately, enabling other processes to access it without modifying the primary catalog file during updates.
35+
36+
37+
38+
## **Primary Catalog YAML File**
39+
40+
If you wish to make adjustments based on the `auto-generated-catalog.yml` file, you can do so by:
41+
42+
- Creating a new `catalog.yml` file in the root of your repository and including only the modifications you want.
43+
- Alternatively, duplicating the entire `auto-generated-catalog.yml` file to the root of your repository and making adjustments as needed.
3044

3145
## Inferring Catalog Item Type
3246

Skyline.DataMiner.CICD.Tools.GitHubToCatalogYaml/CatalogYaml.cs

+5-1
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,11 @@ public class CatalogYaml
5353
" Cannot contain newlines.\r\n" +
5454
" Cannot contain leading or trailing whitespace characters.";
5555

56-
private const string typeComment = "[Required]\r\n" +
56+
private const string typeComment = "WARNING! DO NOT CHANGE THIS FILE.\r\n" +
57+
"Overriding or extending this file can be done by:\r\n" +
58+
" - creating a new catalog.yml file in the root of your repository and writing only the things you want to adjust in there.\r\n" +
59+
" - You may also duplicate this entire file to the root of your repository and then adjust what you want.\r\n\r\n" +
60+
"[Required]\r\n" +
5761
"Possible values for the Catalog item that can be deployed on a DataMiner System:\r\n" +
5862
" - automationscript: If the Catalog item is a general-purpose DataMiner Automation script.\r\n" +
5963
" - lifecycleserviceorchestration: If the Catalog item is a DataMiner Automation script designed to manage the life cycle of a service.\r\n" +

0 commit comments

Comments
 (0)