Canonical location of the Dragonfly API definition
Go to file
dependabot[bot] 2c94e3577d
chore(deps): bump google.golang.org/grpc from 1.48.0 to 1.49.0 (#11)
Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.48.0 to 1.49.0.
- [Release notes](https://github.com/grpc/grpc-go/releases)
- [Commits](https://github.com/grpc/grpc-go/compare/v1.48.0...v1.49.0)

---
updated-dependencies:
- dependency-name: google.golang.org/grpc
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-09-01 11:47:51 +08:00
.github chore: add dependabot actions 2022-08-09 10:39:05 +08:00
hack feat: add security proto (#8) 2022-08-17 16:37:05 +08:00
pkg/apis refactor: security proto (#12) 2022-09-01 11:47:25 +08:00
.gitignore feat: generate grpc proto and mocks 2022-07-29 15:06:10 +08:00
.golangci.yml feat: generate grpc proto and mocks 2022-07-29 15:06:10 +08:00
.markdownlint.yml feat: generate grpc proto and mocks 2022-07-29 15:06:10 +08:00
LICENSE Initial commit 2022-07-28 20:31:19 +08:00
Makefile feat: support recursive download (#3) 2022-08-02 16:31:08 +08:00
README.md docs: readme removes twitter badge 2022-07-29 16:05:42 +08:00
go.mod chore(deps): bump google.golang.org/grpc from 1.48.0 to 1.49.0 (#11) 2022-09-01 11:47:51 +08:00
go.sum chore(deps): bump google.golang.org/grpc from 1.48.0 to 1.49.0 (#11) 2022-09-01 11:47:51 +08:00

README.md

api

Discussions LICENSE

Canonical location of the Dragonfly API definition. The project includes the api definitions of dragonfly services and the mocks of the interface.

Note to developers

If developers need to change dragonfly api definition, please contact dragonfly maintainers.

Community

Welcome developers to actively participate in community discussions and contribute code to Dragonfly. We will remain concerned about the issues discussed in the community and respond quickly.

Contributing

You should check out our CONTRIBUTING and develop the project together.

Code of Conduct

Please refer to our Code of Conduct.