https://github.com/cyscale/grc-cms
Cyscale GRC CMS
https://github.com/cyscale/grc-cms
Last synced: 5 months ago
JSON representation
Cyscale GRC CMS
- Host: GitHub
- URL: https://github.com/cyscale/grc-cms
- Owner: cyscale
- License: mit
- Created: 2022-09-02T14:43:36.000Z (almost 4 years ago)
- Default Branch: dev
- Last Pushed: 2025-06-18T14:49:43.000Z (12 months ago)
- Last Synced: 2025-06-18T15:42:56.240Z (12 months ago)
- Language: HTML
- Homepage: https://cyscale.com
- Size: 3.63 MB
- Stars: 2
- Watchers: 6
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# grc-cms
### Branches
- dev - Development branch where the netlify cms will push the queries, controls and policies changes.
- main - Production branch where changes are going to be pushed by pull requests created from the development branch.
### Flow
When a new push event is sent to either `dev` or `main`, a new workflow is going to be executed. A job will take each
changed file from the entities' directories (`queries`, `controls`, and `policies`) and will upload it to a storage account blob container.
Then, for each file it will send an event message that contains the file name, the event type (`modified` or `deleted`),
the entity slug, and the entity type (`query`, `control`, and `policy`) to a storage account queue.
### Deploy to Prod
We must rebase the changes from dev to main (or any other branch such as QA). This must be done **locally**, otherwise GitHub creates separate commits due to different authors.
- `git checkout dev`
- `git pull`
- `git checkout main`
- `git pull`
- `git rebase dev` (or the hash of a previous commit if you don't want to deploy the latest changes)
- `git push`
A deployment will automatically be created, but it has to be approved by @andreimilas or @AndreiStefanie.