Update dist s1 entrypoints

[cmarshak]

Few questions:

1. I am not sure if my command will be problematic without a character in front of run for aws batch.
2. dist_s1_data option in OPERA_DIST_S1_CONFIRMATION is comma separated granules (could be up to 100 granules).

[cmarshak]

@jhkennedy @jtherrmann @asjohnston-asf

[jhkennedy]

Overall, the job spec looks fine.

I don't see it added to any deployments. @cmarshak did you want to add to hyp3-tibet-jpl-test, hyp3-tibet-jpl, and hyp3-nisar-jpl like OPERA_DIST_S1?

[jhkennedy]

This is fine and will roughly translate to something that looks like:

docker run --rm -it ghcr.io/opera-adt/dist-s1:test run ...

[cmarshak]

Want to confirm that the array input for the API (e.g. this passes space separated granules to the CLI i.e.

API {'arg': [<granule_0>, <granule_1>]} --> CLI --arg <granule_0> <granule_1>

That's what seems to happen for INSAR_ISCE as noted here.

[cmarshak]

I don't see it added to any deployments. @cmarshak did you want to add to hyp3-tibet-jpl-test, hyp3-tibet-jpl, and hyp3-nisar-jpl like OPERA_DIST_S1?

I put it in hyp3-tibet-jpl and the corresponding test deployment.

Thanks so much.

Just updated the schema (had DIST_S1 instead of DIST_S1_CONFIRMATION), reduced memory, and ensure we always pass at least two granules.

[cmarshak]

Super appreciate your time @jhkennedy!