Terraform: Content links in module registry cannot be navigated

[mlschechter]

Terraform Version

N/A; this is an issue with the module registry.

For the module terraform-google-kubernetes-engine when viewing the main README, the following text is displayed in the module registry on terraform.io: "There are multiple examples included in the examples folder but simple usage is as follows".

The link for the examples (https://registry.terraform.io/modules/terraform-google-modules/kubernetes-engine/google/examples/) returns a 404 if you click on it.

Terraform Configuration Files

N/A

Debug Output

N/A

Crash Output

N/A

Expected Behavior

The link should take you to the examples

Actual Behavior

A 404 error was displayed by the web site

Steps to Reproduce

1. Go to the page https://registry.terraform.io/modules/terraform-google-modules/kubernetes-engine/google/1.0.0
2. Click on the examples link in the Usage section

Additional Context

N/A

References

https://github.com/terraform-google-modules/terraform-google-kubernetes-engine/issues/130

[justincampbell]

Thanks for the report! This link is a relative link in the README, which works fine if you view it on GitHub, but since we don't expose the entire filesystem of a module in the Terraform Registry, it's not a valid path there.

The Registry team will look at this soon and come up with a solution for these kinds of links. In the meantime, a workaround would be an absolute (github.com) link instead of relative, but I understand this would be less portable.

[mildwonkey]

I am going to close this issue due to inactivity (the important registry folks are well aware!).

If there is still a question, I recommend the the community forum, where there are far more people available to help. If there is a bug or you would like to make a feature request, please open a new issue and fill out the template.
Thanks!

[morgante]

@mildwonkey Does that mean the registry team never plans to fix this?

I don't see why an issue should be closed if it's on the roadmap. I personally am tracking this to see if/when this gets fixed.

[ryan-roemer]

@mildwonkey -- Just checked my project and sub-links are indeed still 404-ing. Is there an upstream issue with the actual registry folks working on it that I can track so I can see when this is fixed? Thanks!

[mildwonkey]

Nothing external, but I'm happy to reopen this issue - I went on a bit of a closing spree yesterday and figured I'd make some mistakes. Apologies for the noise!