Skip to content

About

Actions for configuring a block ingress

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

10 Commits

Folders and files

Repository files navigation

metablock-ingress

build release

Github action for configuring a block ingress. It is a docker action wrapping metablock apply from the metablock python client: every *.yaml file in path describes one block in a space, and blocks are created or updated to match.

Usage

- uses: quantmind/metablock-ingress@v2
  env:
    METABLOCK_API_TOKEN: ${{ secrets.METABLOCK_API_TOKEN }}
  with:
    space: my-space
    org: my-org-id
    path: ingress

Inputs

  • token: Metablock API token, you need to create one on the metablock admin. Alternatively set the METABLOCK_API_TOKEN environment variable.
  • space: Metablock Space name. Alternatively set the METABLOCK_SPACE environment variable.
  • org: Metablock organization id the request acts within. Alternatively set the METABLOCK_ORG_ID environment variable. Required by the API for org-owned spaces.
  • path: directory containing block ingress definitions, defaults to the repository root.

See example/test.yaml for the shape of a block definition.

Releasing

Bump VERSION, add the matching section to docs/release-notes.md and run make release — see release.instructions.md.

About

Actions for configuring a block ingress

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages