You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, the endpoint can only be specified in the Dataset resource. It would be helpful if one could also specify it in the associated secret. We are trying to establish an operator/user wall of sorts. The user knows what bucket and prefix to use, but rarely knows the endpoint url. The operator has more insight into that part of the world.
This would also allow the data to float around the world, independent of a fixed application spec of what bucket/prefix to use.
The text was updated successfully, but these errors were encountered:
Right now, the endpoint can only be specified in the
Dataset
resource. It would be helpful if one could also specify it in the associated secret. We are trying to establish an operator/user wall of sorts. The user knows what bucket and prefix to use, but rarely knows the endpoint url. The operator has more insight into that part of the world.This would also allow the data to float around the world, independent of a fixed application spec of what bucket/prefix to use.
The text was updated successfully, but these errors were encountered: