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

ensure that mirror node and json rpc relay deploys correctly when account init is ran after node start #1149

Open
Tracked by #868
jeromy-cannon opened this issue Jan 13, 2025 · 0 comments · May be fixed by #1154
Open
Tracked by #868
Assignees
Labels
Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. P1 High priority issue. Required to be completed in the assigned milestone.

Comments

@jeromy-cannon
Copy link
Contributor

jeromy-cannon commented Jan 13, 2025

ensure that mirror node and json rpc relay deploys correctly when account init is ran after node start, relay seems to have an option to pass in the operator id/key, is it defaulting to genesis if nothing is passed? we should do a lookup on the operator id/key incase account init has ran

@jeromy-cannon jeromy-cannon added P1 High priority issue. Required to be completed in the assigned milestone. Internal Requirement Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. and removed Internal Requirement labels Jan 13, 2025
@JeffreyDallas JeffreyDallas linked a pull request Jan 14, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. P1 High priority issue. Required to be completed in the assigned milestone.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants