Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#64 : Remove -l flag, move all configuration to yaml, a lot of refact… #65

Merged
merged 2 commits into from Nov 5, 2019

Conversation

bmonkman
Copy link
Member

@bmonkman bmonkman commented Nov 1, 2019

…oring
Mostly done, but I feel like the proto stuff might still need some love.

@@ -10,73 +10,20 @@ import (
"github.com/commitdev/commit0/internal/templator"
)

func TestGenerateJenkins(t *testing.T) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess these cases are covered by the integration tests now anyway, plus the logic inside of the CI generator is much simpler now.

Copy link
Contributor

@Direside Direside left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI stuff looks good. I'm glad I wrote those tests to make sure.

}

func GenerateProtoServiceLibs(config *config.Commit0Config) {
idlRoot := fmt.Sprintf("%s-idl", config.Name)
func GenerateProtoServiceLibs(service config.Service) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Before the idl repo produced would be a single repo that contained all the service idls & generated code split by folders, mainly for sharing protos (such as health) and for ease of use - is the intention to change this to multiple repos?

mkdir -p gen/{{ $language }}
protoc ${PROTO_SOURCES} --{{ $language }}_out=plugins=grpc,paths=source_relative:proto ./proto/health/*.proto
{{- range .Services}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Related to the comment above, if this is removed how are the the service proto generation commands produced?

generate-http:
mkdir -p gen/go
protoc ${PROTO_SOURCES} --grpc-gateway_out=logtostderr=true,paths=source_relative:proto --swagger_out=logtostderr=true:proto ./proto/health/*.proto
{{- range .Services}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same question for above

Copy link
Contributor

@Pritesh-Patel Pritesh-Patel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few questions about proto servuce generation

@bmonkman bmonkman marked this pull request as ready for review November 5, 2019 22:34
@bmonkman bmonkman merged commit 367da9b into master Nov 5, 2019
@bmonkman bmonkman deleted the move-all-config-to-yaml branch November 5, 2019 22:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants