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

Add “default” storage used by all DSR policies by default #1974

Closed
mfbrown opened this issue Dec 2, 2022 · 1 comment · Fixed by #2438
Closed

Add “default” storage used by all DSR policies by default #1974

mfbrown opened this issue Dec 2, 2022 · 1 comment · Fixed by #2438

Comments

@mfbrown
Copy link

mfbrown commented Dec 2, 2022

Today, every DSR policy rule needs to explicitly link to a named “storage destination” that it uses for uploads. This allows the use of different storage destinations for different DSR policies, but in practice the more likely use case is that a customer would want to use the same storage configuration for all their policies.

Ultimately with the eventual UI, the steps for setting up and using a storage location will look like this:

  • Add “default” storage used by all DSR policies by default - this should be explicitly stated on the storage location config itself.
  • Admin UI to configure “default” storage
  • Settings variables to configure “default” storage

This issue will satisfy the final bullet, in the above list, but we can do this work before the UIs are complete.

AC

  • I can specify the default storage location in the config
  • Update the policies to use the default when nothing else is configured.
@adamsachs
Copy link
Contributor

implementation note based on offline conversations --

we should implement the default storage config on the backend in such a way that would allow users to keep multiple storage configs on the system simultaneously, with only one at any time being selected as the active default storage configuration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants