The understandable confusion in the current paradigm is that while the parameter forms describe this parameter as a "client" of type "EarthRangerClient", that in fact only describes what the eventually materialized object will be by the time we get into the body of the task. From the perspective of user-passed parameters, we actually need a string name of a pre-configured EarthRanger data connection.
Dependencies:
Per @Yun-Wu's comment in https://github.com/wildlife-dynamics/ecoscope-workflows/pull/31#discussion_r1650204041, once #47 is resolved, let's make sure that
EarthRangerClientparameters are more descriptively named and described.The understandable confusion in the current paradigm is that while the parameter forms describe this parameter as a "client" of type "EarthRangerClient", that in fact only describes what the eventually materialized object will be by the time we get into the body of the task. From the perspective of user-passed parameters, we actually need a string name of a pre-configured EarthRanger data connection.