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

Add --nodiscover to Quorum command line #319

Merged
merged 1 commit into from
Jul 24, 2024
Merged

Conversation

peterbroadhurst
Copy link
Contributor

I noticed after starting a Quroum developer environment with the CLI it was attempting to peer with the public list of ethereum nodes.
This PR adds the --nodiscover command line option to stop this.

Couple of other minor changes proposes:

  • Moving tessera to its own directory
    • code naming coupling directly to Quorum seemed a little confusing - as it does as a component work with HL Besu as well (even though that hasn't yet been contributed
  • Changing the code checks to Equals(types.PrivateTransactionManagerTessera) for code blocks that are Tessera specific
    • concept of --private-transaction-manager isn't exclusive to Tessera, and this will avoid catching out future contributions that provide other options

Signed-off-by: Peter Broadhurst <peter.broadhurst@kaleido.io>
@@ -236,43 +237,46 @@ func (p *QuorumProvider) DeployFireFlyContract() (*types.ContractDeploymentResul
return p.connector.DeployContract(contract, "FireFly", p.stack.Members[0], nil)
}

func (p *QuorumProvider) buildTesseraServiceDefinition(memberIdx int) *docker.ServiceDefinition {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

only moved this out as it was a big block of in-lined code - no functional change

Copy link
Contributor

@EnriqueL8 EnriqueL8 left a comment

Choose a reason for hiding this comment

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

LGTM

@EnriqueL8 EnriqueL8 merged commit 8a5b02e into main Jul 24, 2024
11 checks passed
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.

2 participants