-
-
Notifications
You must be signed in to change notification settings - Fork 48
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: Additional Client Options #2049
Conversation
Added more client options
added more option, including slasher for Lighthouse as well as removing unused pruning option for Besu
this.item.yaml = this.item.yaml.replace(new RegExp(/\n^.*\/opt\/app\/slasher*$/gm), ""); | ||
} else if (this.item.yaml.includes("--slasher") && !this.item.yaml.includes("/opt/app/slasher")) { | ||
this.item.yaml = this.item.yaml.replace("--slasher","--slasher\n - --slasher-dir=/opt/app/slasher"); | ||
this.item.yaml = this.item.yaml.replace("volumes:" ,"volumes:\n - /opt/stereum/lighthouse-" + this.item.config.serviceID +"/slasher:/opt/app/slasher") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You may run into some issues here.
The problem is, that ansible sometimes messes with the format of the config which may result in something like this:
volumes:
- someVolume
- someVolume
your solution would end up as:
volumes:
- someVolume
- someVolume
- someVolume
Not only that, another problem ist, that users might use another path than the default /opt/stereum
for this service.
fixed formating and custom install volume problem
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm 🚀
Added more client options