Publish state_service.proto in release artifacts

[vsbogd]

state_service.proto is used by snet-daemon client to get information about payment channels.
It is a part of snet-daemon API and it should be published in release artifacts.

[ghost]

all proto files used by Daemon will be moved to an Artifact ( proto files will be downloaded from this artifact ) to an folder in Daemon called proto and referenced accordingly
Snet-cli wiill also download from this artifact

[raamb]

@anandrgitnirman is this completed? Can we close the issue

[vsbogd]

@anandrgitnirman, I don't see .proto files in released artifacts? Could you please clarify which artifact do you mean?

[anandrgitnirman]

will share the details once done, will raise a PR for review , this is work in progress

[vsbogd]

Ok, got it, read it inaccurately first time

[anandrgitnirman]

all protos are now published as part of Daemon release [v0.1.10] (https://github.com/singnet/snet-daemon/releases/tag/v0.1.10) and any future releases
you will find the files under the directory /proto

[vsbogd]

do we have a script to create release artifacts?

[raamb]

Yes, its an AWS code build. It also sets the version in the daemon before the build and tags the release in Github as well.

[vsbogd]

I think it makes sense to add this code into repo as well. Or may be it is already on github, but located in other repo?

[raamb]

Yes, this is part of the infrastructure repo which is private.

…

On Thu, Apr 4, 2019, 14:19 Vitaly Bogdanov ***@***.***> wrote: I think it makes sense to add this code into repo as well. Or may be it is already on github, but located in other repo? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#99 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ApymOWV3jVxO3_gMJGJQX3SygZLAgRXTks5vdbyWgaJpZM4X7s0p> .

[vsbogd]

Any reason why this script cannot be added to this one?

[raamb]

No particular reason except that we wanted to keep all infra related scripts in one place rather than have it distributed across repos, easier to manage them.

[vsbogd]

Ah ok, may be it doesn't matter for now.