Graylog2 / Graylog2/graylog-project-cli

Support for bootstrap/hook scripts

Open
#15 0 comments 0 reactions 0 assignees View on GitHub
feature triaged
Dominant language
Go
Stars
24
Forks
8
PR merge metrics
No merged PRs in 30d

Description

When developers use `graylog-project bootstrap` to clone all repositories the next step is to run `yarn install` and an initial `mvn compile`. These steps are required to run the web server and graylog server development processes from the IDE.

To avoid hardcoding these commands in the CLI, the CLI should check for hook scripts in a default location. (e.g. `hooks/`) A good default might be to check for a script that is named after the CLI command that is executed.

Examples:

- `graylog-project bootstrap`: Check and execute `hooks/bootstrap.sh` if it exists
- `graylog-project checkout`: Check and execute `hooks/checkout.sh` if it exists

In addition to that, the CLI could also check for `_custom.sh` files where developers can add some custom commands. (these files should be in `.gitignore`)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.