DataOps

We are using the protobuf-git configuration as described at https://cloudhut.dev/docs/features/protobuf#git-repository
In our repository the proto-files live within a proto directory, which seems to be very common, and contains 5 levels of nested folders.

Currently KOWL searches only the first 5 levels of the checkout for .proto files, so our last level is not considered.

• Please

Describe the issue

Currently we run the Linter CI for golang repos using the golang-ci-linter binary. But according to the documentation it is faster and better to use the github action.
https://golangci-lint.run/usage/install/

The UX of all the error highlighting is also better.

What if we do not do this?

Finding linter errors is troublesome as users have to parse through the cons

We're using marshmallow to parse whylogs config from YAML

However, Pydantic is much more powerful as it allows users to set config via various mechanims, from YAML, JSON to Environment settings.

We should consider moving to pydantic

Sending a rest call to delete a job specification throws 404 where as grpc call works fine. Steps to reproduce

curl -X DELETE "http://localhost:9100/v1/project/my-project/namespace/kush/helloworld" -H  "accept: application/json"

Support copy into queries

Currently, both Kafka and Influx sink logs only the data(Row) that is being sent.

Add support for logging column names as well along with data points similar to the implementation in log sink.

This will enable users to correlate the data points with column names.

Zap configurations should be pushed to grpc middleware here: cmd/setup.go#L47

In golang client, consumers get dynamic message instance after parsing. Add an example in the docs on how to use dynamic message instance to get values of different types in consumer code.

List of protobuf types to cover

• timestamp
• duration
• bytes
• message type
• struct
• map

Describe the bug

"client not configured." error is printed even after the config init step.

❯ ./guardian config init
config created: /Users/sushmithbhatta/.config/odpf/guardian.yml
client not configured. try running `guardian config init`

To Reproduce
Steps to reproduce the behavior:

1. Remove ~/.config/odpf/guardian.yml file if exists in local
2. Run `guard

Siren creates alertmanager config and sycns with alertmanger. The alert manager config can change for the same subscriptions if their order changes. We should follow some sorting conventions and stick to those conventions to create an alert manager config.

See:

position
positionUTF8
positionCaseInsensitive
positionCaseInsensitiveUTF8

etc...