You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Noticed a bit of odd behavior when testing out the destination url parameter. If I submit a request where a portion of the destination url is uppercase (in my example, the dataset shortname), the results end up creating two keys in my s3 bucket one is uppercase like in my request and the other is lowercased. The lowercase key contains the harmony-job-status-link object and the uppercase key contains the request results.
Only the harmony-job-status-link object is created under the lowercased opera_l3_dswx-s1_v1 path. I would expect the object to all be created under the same path that matches the case specified in the request.
The text was updated successfully, but these errors were encountered:
Noticed a bit of odd behavior when testing out the destination url parameter. If I submit a request where a portion of the destination url is uppercase (in my example, the dataset shortname), the results end up creating two keys in my s3 bucket one is uppercase like in my request and the other is lowercased. The lowercase key contains the
harmony-job-status-link
object and the uppercase key contains the request results.Example query:
https://harmony.uat.earthdata.nasa.gov/C1264760805-POCLOUD/ogc-api-coverages/1.0.0/collections/all/coverage/rangeset?forceAsync=true&destinationUrl=s3%3A%2F%2Fsvc-bignbit-sit-harmony-staging%2Fbignbit-harmony-output%2FOPERA_L3_DSWX-S1_V1%2F20241212&granuleId=G1272632541-POCLOUD&width=720&height=360&format=image%2Fpng
The destination url is
s3://svc-bignbit-sit-harmony-staging/bignbit-harmony-output/OPERA_L3_DSWX-S1_V1/20241212
This results in the following objects:
Only the
harmony-job-status-link
object is created under the lowercasedopera_l3_dswx-s1_v1
path. I would expect the object to all be created under the same path that matches the case specified in the request.The text was updated successfully, but these errors were encountered: