Export resource-query
for use by other projects?
#869
SteVwonder
started this conversation in
Ideas
Replies: 1 comment
-
We have fluxion-go bindings that can partially address this now, and several examples of using them for (what comes down to) small applications that are similar to resource query, although they aren't currently interactive (e.g., with the terminal input).
These are actually more generic use cases of the same design - not even for resource graphs, but other things (ice cream, topology, and archspec, respectively). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For projects like
flux-coral2
, it could be useful to have access toresource-query
for testing that certain jobspecs will work on a given resource file for a given match policy. We could always put some of those tests into the flux-sched repo (like we did with the MTL tests), but if you are dynamically generating a JGF from a DWS API and want to test that JGF withresource-query
, that is harder to do with that workaround. At the same time, it probably doesn't make sense to have aflux resource-query
command exposed to users. I'm curious what other projects do in this scenario.Beta Was this translation helpful? Give feedback.
All reactions