Skip to content

docs: enable Explorer API docs for TFE #659

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

Closed
wants to merge 1 commit into from

Conversation

notchairmk
Copy link
Member

Enables API docs for Explorer for TFE

https://hashicorp.atlassian.net/browse/TF-26731

@notchairmk notchairmk requested a review from a team as a code owner July 30, 2025 18:11
Copy link

github-actions bot commented Jul 30, 2025

Vercel Previews Deployed

Name Status Preview Updated (UTC)
Dev Portal ✅ Ready (Inspect) Visit Preview Wed Jul 30 18:31:49 UTC 2025
Unified Docs API ✅ Ready (Inspect) Visit Preview Wed Jul 30 18:26:10 UTC 2025

Copy link

Broken Link Checker

No broken links found! 🎉

@rkoron007
Copy link
Contributor

@notchairmk You totally have the correct idea about this, the only thing is the new 1.0.0 release of TFE has been cut in the web-unified-docs-internal repo (App deadline was technically last Friday):
https://github.com/hashicorp/web-unified-docs-internal/pull/299

So, we could handle this in one of two ways:

  1. Merge this in now, then rerun the TFE workflow to get these changes into the new release version (I believe this would work, but we'd need to double check with @RubenSandwich)
  2. Manually add these files in a PR branching off of the new 1.1 release (branch name: tfe-release/1.0.0) in the web-unified-docs-internal repo.

Also @trujillo-adam in case I'm missing anything or misunderstanding the current TFE workflow.

@notchairmk
Copy link
Member Author

🙂 either way works for me

@RubenSandwich
Copy link
Contributor

@rkoron007 @notchairmk I believe either way would work. I slightly lean towards #2, as the workflow still has some rough edges so I'm not 100% that it will work. 😢

@notchairmk
Copy link
Member Author

Closing, this was merged in the other repo

@notchairmk notchairmk closed this Aug 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants