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
Unused subscription name in subscriptions/<account>/<name>/Rules/States
endpoint
#6345
Comments
@cserf do you remember the reasoning here, or was this just a mistake? |
That's a mistake. |
Am I missing something or is this fix simply a matter of parsing the name to the api thusly: def generate(vo):
- for row in list_subscription_rule_states(account=account, vo=vo):
+ for row in list_subscription_rule_states(name=name, account=account, vo=vo):
yield dumps(row, cls=APIEncoder) + '\n' If so, I can do this right away |
alexanderrichards
added a commit
to alexanderrichards/rucio
that referenced
this issue
Dec 12, 2023
bari12
pushed a commit
that referenced
this issue
Jan 23, 2024
rdimaio
pushed a commit
to rdimaio/rucio
that referenced
this issue
Jan 23, 2024
rdimaio
pushed a commit
to rdimaio/rucio
that referenced
this issue
Jan 24, 2024
voetberg
pushed a commit
to voetberg/rucio
that referenced
this issue
Mar 21, 2024
voetberg
pushed a commit
to voetberg/rucio
that referenced
this issue
Apr 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The endpoint requires specifying a subscription name
rucio/lib/rucio/web/rest/flaskapi/v1/subscriptions.py
Lines 626 to 627 in fc3973a
However, it returns rule states for all subscriptions for the provided account
rucio/lib/rucio/web/rest/flaskapi/v1/subscriptions.py
Lines 532 to 534 in fc3973a
So technically, a request to
https://rucio-server.com/subscriptions/jdoe/HOLWAMJFDRSI/Rules/States
is a valid requestSteps to reproduce
Make a request to
https://rucio-server.com/subscriptions/validAccount/invalidSubscription/Rules/Satetes
Rucio Version
32.x
Additional Information
Depending on how this feature is fixed, we might have to make changes in the new webui. We also need to make sure that the change is backward compatible with older clients.
The text was updated successfully, but these errors were encountered: