Http Client Snap vs REST Post snap

[alchemiz]

Hi SMEs,
Good day, with the upcoming deprecating REST snaps currently migrating some of my ultra task to Http Client snap but Http Client snap needs to have at least 1 output view, while REST post snap can have 0 output view

Question: Is there a snap that I can use to close/disregard the Http Client snap output? I tried Exit snap but it has a threshold limit which I can't use since the pipeline is an ultra task and can get x number of requests. 
I did use a filter snap and it works fine just wondering if there's a better snap that can have a 0 output view 

*** Ultra pipeline using http client snap

with Filter snap that block's the http client snap output 

Output:

*** Ultra pipeline using rest post snap

Output

~EmEm

[alchemiz]

Output from ultra task using rest post snap

[koryknick]

@alchemiz - we run into this situation regularly where you want to end a pipeline with a closed output view but the last snap in the pipeline requires at least one output view.  The simple solution is to pull in a Script snap and just remove the output view from it.  Make sure you click on the Edit Script button to allow it to generate the template code. 

You may also want to update to code to remove the output.write() method to prevent any potential issues of trying to write a view that doesn't exist.  It won't fail if you don't do this, it's just a good practice.