iris-connect / eps

Our endpoint system (eps) that manages and secures the communication between different actors in the IRIS connect ecosystem. Think of it as a distributed service mesh router as well as a decentralized message broker. Still evolving, use with caution.
https://iris-connect.github.io/eps/docs/
GNU Affero General Public License v3.0
12 stars 2 forks source link

Build dev docker-images #10

Closed tboegner closed 3 years ago

tboegner commented 3 years ago

Currently we have no separation between services, a push to master triggers build and push to registry for all services.

adewes commented 3 years ago

Does this make the existing workflow (https://github.com/iris-connect/eps/blob/master/.github/workflows/build-and-push-docker-images.yml) obsolete?

lucky-lusa commented 3 years ago

I think we might not need this. There is no need to have develop images for rapid deployment of eps. I think we should always update eps manually on our gateways.

tboegner commented 3 years ago

Does this make the existing workflow (https://github.com/iris-connect/eps/blob/master/.github/workflows/build-and-push-docker-images.yml) obsolete?

No, build-and-push-docker-images.yml is for publishing new release versions. The new workflow was intended for current development versions.

tboegner commented 3 years ago

There is no need to have develop images for rapid deployment of eps.

What about Proxy-Service and Service-Directory, should they also be updated manually?

adewes commented 3 years ago

Do we still need this with the changes to the release process that we've recently made or can we close this?

lucky-lusa commented 3 years ago

No, we do not need this. I will close it.