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

NaBSL prefix needs to be unique #144

Open
shubham-pampattiwar opened this issue Jan 22, 2025 · 1 comment · May be fixed by #172
Open

NaBSL prefix needs to be unique #144

shubham-pampattiwar opened this issue Jan 22, 2025 · 1 comment · May be fixed by #172

Comments

@shubham-pampattiwar
Copy link
Member

We need a unique prefix per NaBSL object so as to avoid scenarios for proper functioning of NaSYNC controller. This would ensure that every NaBSL has a unique S3/object storage URL.

@mpryc
Copy link
Collaborator

mpryc commented Jan 30, 2025

We need to think about scenario where system administrator would want to enforce prefix.

I think that NAC prefix should be second, just after what user or system/administrator specifies. If nothing is being specified by the user or enforced by the administrator then it's just NAC prefix. This way we will allow nicely to see them in the s3 storage.

Example:
prefix from the Spec (specified by the user or by the system administrator): someprefix
resulting prefix: someprefix--

The part is the original BSL path.

@shubham-pampattiwar shubham-pampattiwar self-assigned this Feb 3, 2025
@shubham-pampattiwar shubham-pampattiwar moved this from Todo to In Progress in OADP Feb 4, 2025
@shubham-pampattiwar shubham-pampattiwar moved this from In Progress to Ready for Review in OADP Feb 6, 2025
@shubham-pampattiwar shubham-pampattiwar linked a pull request Feb 6, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Ready for Review
2 participants