remove S3 watcher deployment (only affects Guardian) #4381
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since we've had queue ingestion (see #4201) running very successfully for almost a year we're removing all its infrastructure (see https://github.com/guardian/editorial-tools-platform/pull/828) and as such we ought to remove the guardian deployment steps relating to S3 watcher too.
This PR of course doesn't include actually removing 'S3 watcher' from this repo, although we'd very much like to, we're waiting on another user of the grid (CC @RichardLe @AndyKilmory).