-
Notifications
You must be signed in to change notification settings - Fork 0
Conversation
Removed deprecation notice from camunda repo. Removed now invalid parts like gateway protocol generation and docker image build.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two comments but lgtm.
|
||
# Development | ||
|
||
If we had a gateway-protocol change we need to make sure that we regenerate the protobuf file, which is used by the go client. | ||
In order to do this please follow [this guide](../../gateway-protocol-impl/README.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No helper guide anymore for this? Can we still link that somehow?
It's certainly quite useful to have. I think I used it from time to time and still needed support with it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is not setup yet to generate the protocol stub, this will be handled separately see Phase 1 of camunda/camunda#21817
It's also not crucial now as there are no changes planned to the GRPC protocol going forward.
Adds CI to run on main and PRs.
The following stages are equivalent to their base from camunda/camunda:
go-client
(run tests) andgo-lint
.The
go-apidiff
job was previously comparing the Go client state to the latest stable branch, I went for protecting from breaking changes on each PR instead. As there are not existing releases on this new repo.Instead of using as freshly built Zeebe image for the integration tests I went for referencing the latest 8.6.0-alpha5 release, also instructing test containers to automatically pull it.
Note: I'm making progress on this repo until we have the community hub repo created see camunda-community-hub/community#159