Add support for partners #284
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
KaloyanTanev
force-pushed
the
kalo/update-cdvn-with-latest-changes
branch
from
ac35e6c
to
b9e9aab
Compare
KaloyanTanev
force-pushed
the
kalo/update-cdvn-with-latest-changes
branch
from
4846d29
to
d08f4d5
Compare
Base automatically changed from
kalo/update-cdvn-with-latest-changes
to
main
September 26, 2024 12:05
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for partners - easier overriding of env variables and docker compose files.
Implement Lido as first partner.
Up until now Lido has been using lido-charon-distributed-validator-node repository, however, this creates a lot of discrepancies. Having a single repository is easier to manage and keep up to date.
N.B.: This PR is on top of #283 , that is because #283 is reworking the repository in a lot of places and it's best to be used as a ground. However, adding those changes to #283 is not suitable as it this one introduces new featureset.