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

Make etcd_bin_prefix configurable #139

Open
EtienneM opened this issue Feb 23, 2023 · 0 comments
Open

Make etcd_bin_prefix configurable #139

EtienneM opened this issue Feb 23, 2023 · 0 comments
Labels
Feature Request Enhancement to existing functionality or new functionality

Comments

@EtienneM
Copy link

EtienneM commented Feb 23, 2023

🗣️ Foreword

Thank for taking the time to fill this feature request fully. Without it we may not be able to , and the issue may be closed without resolution.

🙍 Problem Statement

I would love to be able to configure the folder where the etcd binaries are installed. We want to install two different versions on a single server.

❔ Possible Solution

I can see that the etcd_bin_prefix is currently hard coded:

def etcd_bin_prefix
'/usr/bin'
end

We would like to make it a property, just like the version for instance.

This prefix should also be configurabe in etcd_service_manager_systemd.

If this is something interesting for you, we developed a PR (Scalingo#1) which can be backported here.

⤴️ Describe alternatives you've considered

We considered using etcd_installation_docker (rather than etcd_installation_binary currently) but it would be a lot of work. Moreover it seems impossible to change the mounted volumes but we need it to mount the TLS files inside the etcd container.

➕ Additional context

n/a

@EtienneM EtienneM added the Feature Request Enhancement to existing functionality or new functionality label Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Enhancement to existing functionality or new functionality
Projects
None yet
Development

No branches or pull requests

1 participant