| Steps to Reproduce: |
# Provision data sync
# Add simple schema using subscriptions to UI [e.g. this one|https://gist.github.com/jhellar/b580cd5482fca0f5bf3f7c6c2474fdec]
# Add resolver for some mutation, connect it to subscription and save the resolver
# In postgres db, you should see a record of the subscription (Run {{psql -U postgres -d aerogear_data_sync_db -c 'select * from "Subscriptions"'}} in postgres pod)
# Now remove the subscription from resolver
Result: The record should disappear from DB but it's still present
Now if you remove subscription from the schema or rename it, it causes serious problem with starting the server after steps above are performed
{code}
{"level":50,"time":1537362790754,"msg":"\"Subscription\" defined in resolvers, but not in schema","pid":19,"hostname":"data-sync-server-1-2t8pv","type":"Error","stack":"Error: \"Subscription\" defined in resolvers, but not in schema","v":1}
{"level":50,"time":1537362790754,"msg":"[object Promise]","pid":19,"hostname":"data-sync-server-1-2t8pv","type":"Error","stack":"Error: \"Subscription\" defined in resolvers, but not in schema","v":1}
{code} |
