Update Scripts With FC REST Updates

[ric-evans]

closes #31

[blinkdog]

LGTM.

Out of scope for this PR, but I wonder since we're (re)using the logical_name + query construct, if we should add a query shortcut inside the FC to mean this?

[ric-evans]

LGTM.

Out of scope for this PR, but I wonder since we're (re)using the logical_name + query construct, if we should add a query shortcut inside the FC to mean this?

It's a good idea since we're making it a construct here. But I'm hesitant to introduce more abstraction to the query interface considering we've departed the "logical_name=locations.path" paradigm. Really, this 2-arg construct is a stop-gap measure since locations.path is not currently suitably indexed to be the sole argument. I do see the benefit of introducing a location-path shortcut key (or similar) that bypasses the "query" argument.

[ric-evans]

LGTM.
Out of scope for this PR, but I wonder since we're (re)using the logical_name + query construct, if we should add a query shortcut inside the FC to mean this?

It's a good idea since we're making it a construct here. But I'm hesitant to introduce more abstraction to the query interface considering we've departed the "logical_name=locations.path" paradigm. Really, this 2-arg construct is a stop-gap measure since locations.path is not currently suitably indexed to be the sole argument. I do see the benefit of introducing a location-path shortcut key (or similar) that bypasses the "query" argument.

Note: I'm not sure if we'll ever get this version of the FC to index locations.path well. It's something that Clowder may be able to do.