Report deleted configurations when reporting changed configurations

[jml]

From @jml on January 24, 2017 18:31

We currently have private operations for getting changed and created configs. We use this in the recording rules server to make sure we're processing all the configs.

We should also report the IDs of the configs that have been deleted, so we can stop processing those rules.

Copied from original issue: weaveworks/service#1085

[lelenanam]

@jml can we do this by creating new deleted config (the same as last one but with DeletedAt is not null) on deletion and creating new not deleted config for restoring config (the same as last config but with DeletedAt is null)?

[jml]

I think that would work, yes.

#620 might change the nature of this ticket.

[bboreham]

Ah, I think I just wrote a longer version at #629 (comment)

[bboreham]

I believe #629 fixed this.