You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The eventhook for the annotationdelete will fail because it is expecting only a singular deletion.
We receive the following error
"object doesn't have an id "
To Reproduce
Code up a delete resolver to delete all based on some predicate
Expected behavior
For the delete eventhook to be able to handle > 1 deletions of an thing at a time, rather than having to iterate and DeleteOne(id) at a time within the resolver.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
# Summary
Wire up new permissions checks for the annotation/status namespaces
- [x] Fix 🐛 ensuring we cannot set an empty `resourceProviderID` for a
status namespace
- [x] Add in events and other boilerplate for the test db setup; wire up
the ent hooks
- [x] Mock permissions in all the resolver unit tests
- [x] Add oidc auth test to verify access with and without oidc enabled
- [x] Add unit test for status namespace
[Issue](infratographer/x#152) found with event
hooks and deleting multiple things from the db in one shot. Worked
around it by deleting one record at a time.
---------
Signed-off-by: Matt Siwiec <[email protected]>
Describe the bug
Say for example, we are deleting an
annotationNamespace
and all of it's associatedannotations
within one call to theent
client.The
eventhook
for theannotation
delete
will fail because it is expecting only a singular deletion.We receive the following error
To Reproduce
Code up a delete resolver to delete all based on some predicate
Expected behavior
For the delete eventhook to be able to handle > 1 deletions of an thing at a time, rather than having to iterate and
DeleteOne(id)
at a time within theresolver
.Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: