-
Notifications
You must be signed in to change notification settings - Fork 20
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
renterd config
enables S3 when not asked
#1612
Comments
Right now saying "no" to "Would you like to configure X" doesn't mean that X gets disabled but rather that you don't configure it and accept the defaults. Which for S3 is "enabled". We can follow up with another prompt "Would you like to enable the S3 gateway" though which can then be used to enable/disable S3 explicitly. The default is "enabled" because there is no harm in doing so. Without creating any keys, nothing can access the gateway. |
Current Behavior
The setup wizard of
renterd config
asks whether I want to configure the S3 settings. If I say "no", it still generates arenterd.yml
file wheres3: enabled
equals totrue
.Expected Behavior
If I tell
renterd config
that I do not want to configure the S3 settings, I imply that I do not want to enable S3. Therefore, it needs to be disabled in the config file.Steps to Reproduce
renterd config
.Version
v1.1.0-beta.5
What operating system did the problem occur on (e.g. Ubuntu 22.04, macOS 12.0, Windows 11)?
Ubuntu 24.04
Autopilot Config
N/A
Bus Config
N/A
Contract Set Contracts
N/A
Anything else?
No response
The text was updated successfully, but these errors were encountered: