fix: Use correct path for results exporter

[bradbeam]

Signed-off-by: Brad Beam brad.beam@stormforge.io

[bradbeam]

we should look at modifying this workflow at some point to do a build without push on pr

[charandas]

Actually, we decided to use relative paths as a convention when in the same repo, unless there is reason to fully qualify in this case?

[charandas]

Same comment as the other one.

[charandas]

Aha! Looks like you are going the other way. On the last PR from Tibo, we assumed people will clone the whole repo before running any of these examples.

But I do realize now, that integration tests would be one thing happening outside of this repo; is that where kustomize would break when using relative paths; I am not sure and would need to check.

[charandas]

@bradbeam I confirmed kustomize handles github top-level path just fine, with the included kustomizations referring to relative paths. IMO, this way is the only way to guarantee what version one wants from the top level using a git sha, for instance.

If you fully qualify the paths inside the repo with github.com/..., you will always get the included paths with ref set to HEAD/main.

# This is working currently, and it uses relative paths
kustomize build github.com/thestormforge/examples/webserver/locust-metrics