bazel query @maven//: despite repository-name: enola_maven

[vorburger]

#401 related follow-up:

E.g. this has:

[DefaultDispatcher-worker-2] INFO org.virtuslab.bazelsteward.core.common.CommandRunner - bazel query @maven//:outdated.repositories --output xml --noshow_progress
[main] ERROR org.virtuslab.bazelsteward.maven.MavenDependencyKind - Failed to extract used maven dependencies. Bazel Steward supports rules_jvm_external 4.0 or newer
[main] WARN org.virtuslab.bazelsteward.app.App - Error happened during detecting available versions for maven. Skipping this dependency kind...
[main] WARN org.virtuslab.bazelsteward.app.App - Error details: bazel query @maven//:outdated.repositories --output xml --noshow_progress
ERROR: No repository visible as '@maven' from main repository

despite repository-name: enola_maven here.

Might this have been an oversight in #402 ?

[vorburger]

Actually, this worked great locally; but it's for some strange reason is not working (only) on the GitHub Action (for me).

Perhaps it's for some reason not reading my .bazel-steward.yaml when running on the GitHub Action?!

Perhaps it's someone running an older version of it when running on the GitHub Action?!

[vorburger]

Perhaps it's for some reason not reading my .bazel-steward.yaml when running on the GitHub Action?!

That's it! Here it says:

"By default, Bazel Steward looks for the configuration file in the root of the git repository under one of the following names:"

but then here it starts with --config-path '${{ inputs.configuration-path }}' which here defaults to ./bazel-steward.yaml. But mine is named .bazel-steward.yaml here. Subtle but important difference.

This can probably be worked around by explicitly setting that configuration-path. But in a perfect world, it should probably be more consistent.

IMHO, it should probably better fail when started with a --config-path that it's not actually able to read from.

[lukaszwawrzyk]

Indeed it should fail if path is passed explicitly, I fixed that. The default value for github action is not ideal. I think we should leave it empty and the action, if config value is empty, should not pass the flag at all.

[vorburger]

👉 #434