-
Notifications
You must be signed in to change notification settings - Fork 524
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
Revisit configuration defaults for object storage #528
Comments
I see this issue as 'checked off' in #367 which implies that it is done, yet this github issue is still open and I don't see a linked PR. |
@pracucci -- Sorry I linked the wrong 367 hehe: I was referring to the fact that I see a checkmark next to the line item for this issue in our parent tracker, but that the underlying issue is still open. Sounds like from your comment, the checkmark should be removed and the work still needs to be done. See screenshot - generally I would only expect a check mark next to an issue that has been closed. @pracucci since this issue as is is quite broad, can you provide a little more description? What should an engineer be looking for when revisiting the defaults? Are we trying to enforce certain specific values? If so, which ones? |
I have no idea what we wanna do here :) It wasn't added by me. I think it was by @simonswine . |
When I added this to the epic issue list, I mostly meant this to be covering the switch from I am otherwise not too much aware what changes we should make to those flags. I have never used
|
In the Cortex project we had some people using Swift, and it was working for them, so I wouldn't touch it :) |
I think from my point of view we can close this then. |
Agreed. |
No description provided.
The text was updated successfully, but these errors were encountered: