Skip to content

Commit 129ee99

Browse files
Improved Documentation .
Addressing issue #363 - Added details about the `generated.yaml` file in `Development.md`, specifying that it is built via the DevSecOps-MaturityModel-data repository. - Moved the procedure for generating `generated.yaml` to the root `README.md`, ensuring clear setup instructions. - Included npm/yarn commands for building the file. - Suggested potential reorganization of `README.md` or the creation of an `INSTALL.md` for better documentation clarity. This update enhances onboarding clarity and ensures contributors can generate necessary YAML files seamlessly.
1 parent b4523a5 commit 129ee99

File tree

3 files changed

+38
-22
lines changed

3 files changed

+38
-22
lines changed

Development.md

Lines changed: 14 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ This guide walks you through **setting up the project locally**, making contribu
99

1010
## **Project Setup**
1111

12-
### Development Server :-
12+
### Development Server
1313

1414
The DSOMM is based [Angular](https://angular.dev/) and uses npm for package management.
1515

@@ -45,20 +45,28 @@ curl https://raw.githubusercontent.com/devsecopsmaturitymodel/DevSecOps-Maturity
4545

4646
- Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The application will automatically reload if you change any of the source files.
4747

48-
### Code scaffolding :-
48+
## Code Scaffolding
4949

5050
Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module`.
5151

52-
### Build :-
52+
## Build
5353

5454
Run `ng build` to build the project. The build artifacts will be stored in the `dist/` directory.
5555

56-
### Running unit tests :-
56+
## Running Unit Tests
5757

5858
Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.io).
5959

60-
### Coding Style Conventions :-
60+
## Coding Style Conventions
6161

6262
- We follow the coding style defined by [ESLint](https://eslint.org/).
6363
- We also use [Prettier](https://prettier.io/docs/en/index.html) as our opinionated code formatter.
64-
- To validate the schemas of the DSOMM yaml files in the IDE, it is recommended to use the VS Code extension [redhat.vscode-yaml](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml). The schemas are stored in /src/assets/YAML/schemas
64+
- To validate the schemas of the DSOMM yaml files in the IDE, it is recommended to use the VS Code extension [redhat.vscode-yaml](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml). The schemas are stored in `/src/assets/YAML/schemas`
65+
66+
### Running Linter
67+
68+
Run `ng lint` to run the linter from the command line.
69+
If you want to lint only a specific component, use:
70+
71+
```bash
72+
ng lint --lint-file-patterns .\src\app\component\xxxxxx\

README.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,29 @@ service docker start
9494
docker run -d -p 80:8080 wurstbrot/dsomm:latest
9595
```
9696

97+
## Generating the `generated.yaml` File
98+
99+
The `generated.yaml` file is dynamically created during the build process. If you don’t see this file after setup, follow these steps to generate it:
100+
101+
**1. Clone the Required Repository:**
102+
The `generated.yaml` file is built via the DevSecOps-MaturityModel-data repository. Make sure you have cloned and set it up correctly.
103+
104+
**2. Run the Build Command:**
105+
Navigate to the project directory and run the following command:
106+
- *Using npm:*
107+
108+
```sh
109+
npm run build
110+
````
111+
112+
- *Using yarn:*
113+
114+
```sh
115+
yarn build
116+
```
117+
118+
*If the file is missing, ensure all dependencies are installed and that you have the correct access to the `DevSecOps-MaturityModel-data` repository.*
119+
97120
## Activity Definitions
98121
The definition of the activities are in the [data-repository](https://github.com/devsecopsmaturitymodel/DevSecOps-MaturityModel-data).
99122

src/assets/YAML/generated/README.md

Lines changed: 1 addition & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -8,19 +8,4 @@ It stores configuration settings and other automatically generated data used by
88
- It is a machine-generated file that is **not meant to be manually edited**.
99
- It helps in **storing configuration settings**, which are loaded at runtime.
1010
- Used by the application to dynamically configure settings.
11-
12-
## **How is it Generated?**
13-
14-
The `generated.yaml` file is created as part of the DevSecOps Maturity Model’s **build process**. If you don’t see this file after setup, make sure to run:
15-
16-
```sh
17-
npm run build
18-
```
19-
20-
or
21-
22-
```sh
23-
yarn build
24-
```
25-
26-
This will generate the required **YAML** file.
11+
- This file is generated via the [DevSecOps-MaturityModel-data](https://github.com/devsecopsmaturitymodel/DevSecOps-MaturityModel-data) repository.

0 commit comments

Comments
 (0)