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

removing a failing system and integration will still cause a request to fail #3769

Closed
Roger-Ethyca opened this issue Jul 10, 2023 · 4 comments · Fixed by #3771
Closed

removing a failing system and integration will still cause a request to fail #3769

Roger-Ethyca opened this issue Jul 10, 2023 · 4 comments · Fixed by #3771
Assignees
Labels
bug Something isn't working

Comments

@Roger-Ethyca
Copy link
Contributor

Bug Description

even after removing a failing system and integration will still cause a request to fail

Steps to Reproduce

  1. create a system from add a system
  2. click on the integrations tab and add an integration (i used domo which will fail connection test once creds are added)
  3. add a new system and integration (i used friendbuy nextgen)
  4. process a access your data request submitted through the privacy center (it will error on domo)
  5. go to view systems and remove the domo system
  6. reprocess the request

Expected behavior

the request still errors on domo

Screenshots

If applicable, add screenshots to help explain your problem.

Environment

  • Version:
  • OS:
  • Python Version:
  • Docker Version:

Additional context

Add any other context about the problem here.

@Roger-Ethyca Roger-Ethyca added the bug Something isn't working label Jul 10, 2023
@adamsachs
Copy link
Contributor

adamsachs commented Jul 10, 2023

after doing some initial investigation, it's worth noting that this isn't even specifically tied to reprocessing an existing privacy request. this seems to impact any new, future privacy request too.

this implies a bigger impact to users, and also a different root cause technically - it doesn't have anything to do with request reprocessing, it's some artifact from the deleted system/integration being left around generally, not something tied to a particular request state.

@adamsachs
Copy link
Contributor

on first glance, it looks like the problem here is that both the connectionconfig and the datasetconfig records are left in tact even after deleting the system (the ctl_systems record is properly removed).

in request_runner_service.py we pretty basically just query for all DatasetConfig and ConnectionConfig records to create our execution graph.

at this point it's probably worth clarifying expectations, since i do notice that the "old" connection still exists in the "connection manager" screen. do we expect deleting a system to effectively also delete its integration, or should users have to go into the connection manager and explicitly delete the integration? if it's the former, then i think we'll need to update the system delete operation to remove these "integration" artifacts from the db (either by making multiple API calls from the FE or adjusting the API on the BE.

@rsilvery
Copy link
Contributor

They won't be able to use the connection manager anymore so, yes, deleting a systems should delete the connection/integration.

@Roger-Ethyca
Copy link
Contributor Author

moving to done

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.

3 participants