Allow components to deviate from consolidated object storage settings without disabling consolidated object storage completely
Proposal
Right now, if any of the components using object storage specifies their own object storage settings, the consolidated object storage is ignored completely. This was an initial design decision to avoid the situations where the component and Workhorse disagree on where the file should be and what the credentials are. This issue proposes a revisit to that decision.
Two proposals:
- Allow users to deviate any component from consolidated object storage, understanding the risks associated with it. There is no higher risk because users were doing this before we had consolidated object storage in place.
- Allow users to deviates specific components, that do not use Workhorse acceleration, from consolidated object storage.
/cc @stanhu
Edited by Balasankar 'Balu' C