#3459 [Core feature] add more intuitive methods to `FlyteRemote` class for gate nodes Issue created by cosmicBboy Motivation: Why do you think this is important? The purpose of this issue is to make it more intuitive to use

FlyteRemote

for providing input values for

wait_for_input

and

approve

gate nodes. Goal: What should the final outcome look like, ideally? Proposal Add three new methods: • `FlyteRemote.approve(<signal_id>, <execution_name>, project=None, domain=None)`: sets this approve gate node to True • `FlyteRemote.reject(<signal_id>, <execution_name>, project=None, domain=None)`: sets this approve gate node to False • `FlyteRemote.set_input(<signal_id>, <execution_name>, <value>, project=None, domain=None, python_type=None, literal_type=None)`: sets the input of a

wait_for_input

gate node to

<value>

Describe alternatives you've considered Continue with the currently

FlyteRemote.set_signal

implementation. Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? • Yes Have you read the Code of Conduct? • Yes flyteorg/flyte