Tiltfile OUTPUT_TO_NULL_COMMAND not recognized on Windows about application-accelerator-samples HOT 3 OPEN

another option is to use apply_cmd_bat as well in the tiltfile
the relevant part could look like:

  apply_cmd="tanzu apps workload apply -f config/workload.yaml --debug --live-update" +
            " --local-path " + LOCAL_PATH +
            " --source-image " + SOURCE_IMAGE +
            " --namespace " + NAMESPACE +
            " --build-env BP_DEBUG_ENABLED=true" +
            " --yes " +
            " > /dev/null " +
            " && kubectl get workload " + NAME + " --namespace " + NAMESPACE + " -o yaml",
  apply_cmd_bat="tanzu apps workload apply -f config/workload.yaml --debug --live-update" +
            " --local-path " + LOCAL_PATH +
            " --source-image " + SOURCE_IMAGE +
            " --namespace " + NAMESPACE +
            " --build-env BP_DEBUG_ENABLED=true" +
            " --yes " +
            " > NUL " +
            " && kubectl get workload " + NAME + " --namespace " + NAMESPACE + " -o yaml",

based on tilt docs:

apply_cmd_bat ( Union [ str , List [ str ]]) – If non-empty and on Windows, takes precedence over apply_cmd . Ignored on other platforms. If a string, executed as a Windows batch command executed with cmd /S /C ; if a list, will be passed to the operating system as program name and args.

This will allow the accelerator Tilt config to work on any OS. while i hardcoded the values, there could be 2 VARS set at the top something like:

OUTPUT_TO_NULL_COMMAND_WIN = ' > NUL '
OUTPUT_TO_NULL_COMMAND = ' > /dev/null '

from application-accelerator-samples.

Update: we should be able to override this env var before invoking tilt up (making it runnable on Windows), but in general I'm guessing NUL might be a friendlier default than /dev/null, assuming a majority of folks using this accelerator will be using Windows?

from application-accelerator-samples.

@trisberg I think this issue can be closed now that tanzu apps has added -oyaml

from application-accelerator-samples.