Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TRACKING] TF registry breaks on relative links. #42

Open
dukedave opened this issue May 9, 2019 · 3 comments

Comments

Projects
None yet
2 participants
@dukedave
Copy link
Contributor

commented May 9, 2019

Both xray and vpc submodules give me a 404 Not Found.

The code seems correct per the docs ⬇️ , so it might be a registry problem?

Nested modules should exist under the modules/ subdirectory. Any nested module with a README.md is considered usable by an external user.

@ryan-roemer

This comment has been minimized.

Copy link
Member

commented May 9, 2019

Yeah, the hard thing I don't have a solution for is links in those sub-readmes that work on both GitHub and the TF registry.

@dukedave

This comment has been minimized.

Copy link
Contributor Author

commented May 9, 2019

I think it's gotta be a registry bug, but I don't see one open? 🤔

@ryan-roemer

This comment has been minimized.

Copy link
Member

commented May 10, 2019

Here's a bug filed for registry relative link breakage issue: hashicorp/terraform#20930

It was actually the first thing I noticed after publishing this module the first time :)

@ryan-roemer ryan-roemer changed the title Nested module readme pages are broken on Registry [TRACKING] TF registry breaks on relative links. May 10, 2019

@ryan-roemer ryan-roemer added the bug label May 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.