Skip to content

Releases: grafana/k6registry

v0.1.22

10 Sep 07:29
b48c917
Compare
Choose a tag to compare

k6registry v0.1.22 is here 🎉!

This is an internal maintenance release.

Retry git pull on error

In the git working directory, the file permissions are changed to make the cache persistent in GitHub action mode. As a consequence, the git pull operation will fail (if permissions have actually been changed).

To fix this, if the pull operation fails, the pull operation is repeated after a forced checkout operation.

v0.1.21

10 Sep 06:58
0940973
Compare
Choose a tag to compare

k6registry v0.1.21 is here 🎉!

This is an internal maintenance release.

Retry git pull on error

In the git working directory, the file permissions are changed to make the cache persistent in GitHub action mode. As a consequence, the git pull operation will fail (if permissions have actually been changed).

To fix this, if the pull operation fails, the pull operation is repeated after a forced checkout operation.

v0.1.20

09 Sep 13:49
430be3a
Compare
Choose a tag to compare

k6registry v0.1.20 is here 🎉!

This is an internal maintenance release.

Added verbose logging

  • CLI: added the -v/--verbose flag for verbose logging
  • GitHub action: added verbose input parameter for verbose logging

v0.1.19

03 Sep 16:02
f5c3a2d
Compare
Choose a tag to compare

k6registry v0.1.19 is here 🎉!

This is an internal maintenance release.

simplify responsibility*

  • only use registry.schema.json instead of owning it, registry.schema.json source moved to grafana/k6-extension-registry repository
  • only implement openapi.yaml and not own it, openapi.yaml source moved to grafana/k6-extension-registry repository

v0.1.18

02 Sep 06:12
7692fb3
Compare
Choose a tag to compare

k6registry v0.1.18 is here 🎉!

This is an internal maintenance release.

extension catalog support*

The registry and the catalog contain the same elements, only in different containers. The registry is a list (array), and the catalog is a map (object).

The consequence of this is that the versions property is moved from the repository object to the extension object.

During the generation of registry subsets, catalogs are also generated for the subsets (e.g. cloud.json and cloud-catalog.json).

v0.1.17

30 Aug 16:28
1797d69
Compare
Choose a tag to compare

k6registry v0.1.17 is here 🎉!

This is an internal maintenance release.

Fix file/directory permissions

In GitHub Action mode, the permissions of the cache (XDG_CACHE_HOME) files have been corrected.

In the case of files, now the permission set to 0o644, in the case of a direcotry to 0o755.

v0.1.16

30 Aug 15:45
66af04c
Compare
Choose a tag to compare

k6registry v0.1.16 is here 🎉!

This is an internal maintenance release.

Fix file/directory permissions

The go-git library used to checkout the source of extensions creates certain files readable only for the user. This makes it impossible to cache files created in GitHub action mode between workflow runs.

After the git operations, the workdir file permissions now will be fixed.

In the case of files, now the permission set to 0o644, in the case of a direcotry to 0o755.

v0.1.15

30 Aug 14:52
7d8463b
Compare
Choose a tag to compare

k6registry v0.1.15 is here 🎉!

This is an internal maintenance release.

Fix file/directory permissions

golangci-lint forces the file permission to be 0o600 and the directory permission to be 0o750. When k6registry runs as a GitHub action, it runs as the root user, so accessing the generated files from the rest of the workflow is problematic.

In the case of generated files, now the permission set to 0o644, in the case of a direcotry to 0o755.

v0.1.14

30 Aug 12:21
1405091
Compare
Choose a tag to compare

k6registry v0.1.14 is here 🎉!

This is an internal maintenance release.

Compliance checks

Compliance checks can be performed after each change. When the --lint flag is used, not only the internal linter runs but also the integrated k6lint library.

As a result of the compliance checks, a badge can be generated for each extension based on the compliance grade.

API in the filesystem

By using the --api flag, files are created with relative paths in a base directory with a kind of REST API logic:

  • in the module directory, a directory with the same name as the path of the extension module

    • badge.svg badge generated based on the compliance grade
    • extension.json extension data in a separate file
  • the subdirectories of the base directory contain subsets of the registry broken down according to different properties (tier, product, category, grade)

    docs/example-api
    ├── registry.json
    ├── registry.schema.json
    ├── category
    │   ├── authentication.json
    │   ├── browser.json
    │   ├── data.json
    │   ├── kubernetes.json
    │   ├── messaging.json
    │   ├── misc.json
    │   ├── observability.json
    │   ├── protocol.json
    │   └── reporting.json
    ├── grade
    │   ├── A.json
    │   ├── B.json
    │   ├── C.json
    │   ├── D.json
    │   ├── E.json
    │   ├── F.json
    │   └── passing
    │       ├── A.json
    │       ├── B.json
    │       ├── C.json
    │       ├── D.json
    │       ├── E.json
    │       └── F.json
    ├── module
    │   ├── github.com
    │   │   ├── grafana
    │   │   │   ├── xk6-dashboard
    │   │   │   │   ├── badge.svg
    │   │   │   │   └── extension.json
    │   │   │   ├── xk6-disruptor
    │   │   │   │   ├── badge.svg
    │   │   │   │   └── extension.json
    │   │   │   └── xk6-sql
    │   │   │       ├── badge.svg
    │   │   │       └── extension.json
    │   │   └── szkiba
    │   │       └── xk6-faker
    │   │           ├── badge.svg
    │   │           └── extension.json
    │   ├── gitlab.com
    │   │   └── szkiba
    │   │       └── xk6-banner
    │   │           ├── badge.svg
    │   │           └── extension.json
    │   └── go.k6.io
    │       └── k6
    │           └── extension.json
    ├── product
    │   ├── cloud.json
    │   └── oss.json
    └── tier
        ├── community.json
        └── official.json
    

v0.1.13

23 Aug 09:15
dfec9d4
Compare
Choose a tag to compare

k6registry v0.1.13 is here 🎉!

This is an internal maintenance release.

Add repo metadata for linter support

Add last modification (timestamp) and git clone URL (clone_url) repository metadata to support implementation of extension linter.