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

[ BUG ] V2 redirections need to be updated within the _endpoint module for Uber Class usage (MSSP service collection) #859

Closed
jshcodes opened this issue Dec 16, 2022 · 0 comments · Fixed by #860
Assignees
Labels
bug 🐛 Something isn't working

Comments

@jshcodes
Copy link
Member

Describe the bug
Newly released endpoints for the MSSP service collection are properly redirected within the Service Class, but are not updated within the endpoint module. This results in the Uber Class having to reference the "V2" operation IDs in order to access the new operation.

To Reproduce
Create an instance of the Uber Class and call the generic operation ID for a new operation (Ex: getCIDGroupMembersBy). You will receive results from the deprecated operation.

Expected behavior
Requests from the Uber Class to the generic operation IDs for these operations should redirect to the newly released endpoints.

Environment (please complete the following information):

  • OS: All supported
  • Python: All supported
  • FalconPy: 1.2.6

Additional context
Discovered while updating Flight Control documentation.

@jshcodes jshcodes added the bug 🐛 Something isn't working label Dec 16, 2022
@jshcodes jshcodes self-assigned this Dec 16, 2022
@jshcodes jshcodes changed the title [ BUG ] V2 redirections need to be updated within the _endpoint module for Uber class usage (MSSP service collection) [ BUG ] V2 redirections need to be updated within the _endpoint module for Uber Class usage (MSSP service collection) Dec 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant