-
Notifications
You must be signed in to change notification settings - Fork 0
Github Actions
The cc-template-pack has a few github actions that can be useful for your pack. For security reasons, you must enable github actions for your own repo.
Required action permissions: EndBug/add-and-commit@v9.1.1, actions/checkout@v3
Required inputs:
- API base URL, like https://your-org-name.cribl.cloud/api/ (including the trailing / but not the v1 part)
- Bearer token with access to that instance, see https://docs.cribl.io/stream/api-tutorials/#tokens (just the token, not the Bearer part)
This connects out to a cribl instance where you have installed your pack, Exports your pack from there (in MERGE mode), and imports it into your repository as a new branch. If you like the changes, you can create a pull request to bring that branch into your development process.
Required action permissions: actions/checkout@v3, rlespinasse/github-slug-action@3.5.1, softprops/action-gh-release@5e3f23f92c903aac25270f66388fdcb366c5b549, cardinalby/git-get-release-action@1.1.1
Runs when a tag is pushed that looks like v#.#.# with an optional -RC#
This action creates a .crbl
file that can be used to import your pack into your environment.
Required action permissions: actions/checkout@v3
Runs when new commits are added to the main branch, or can be run manually through the github web UI.
This action looks for files in the repo's local
directory that might be overriding the configurations in default
. Ordinarily, a pack will not deliver any files in local. If you use the pack export feature in merge
mode, and import that .crbl back into your repository, there will not be any files in local either. If you pull in your changes from the worker filesystem, you may end up with local files.