Promote v2 content in docs for deploying with GH Pages #3013
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
We need a new hosting solution for the docs and landing pages.
Solution
OpenLineage uses GitHub, and it works well. Our use case is slightly different because we need to deploy a subdirectory (
v2in docs). GitHub Actions allows you to set an arbitrary path as the source in a YML file in .github/workflows. This adds the YML (auto-generated by GH except for the path) to enable us to publish the site using GH, which is currently not possible using the UI. After this is enabled, we can open a ticket with the LF to point the domain to GH. Instructions for doing this are here. Note: the domain has to be removed from another repo in the org (presumably the website repo) before we can configure the new site, and I don't have access to that repo's settings to do this.Closes: #3014
One-line summary: promote v2 content in docs for GH Pages deploys
Checklist
CHANGELOG.md(Depending on the change, this may not be necessary)..sqldatabase schema migration according to Flyway's naming convention (if relevant)