Refactor v16 documentation for Sphinx #936
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Use latest stable lxd * Test tweaks * Test tweaks
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* Poll all members in the cluster topology script * Dual branch config * Unit tests and bugfixes * Add peers when starting the observer * Retry sync up checks
* Add wal_keep_size config option Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com> * Remove parameter addition Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com> * Reset durability_wal_keep_size value to PG default Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com> --------- Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>
* Refactor headings for syntax best practice * Update the Security section
Co-authored-by: GitHub Actions <41898282+github-actions[bot]@users.noreply.github.com>
* Bump boto * Conditional checksum calculation
* Create tiobe_scan.yaml * Remove push trigger
* Set series for ubuntu-advantage test and disable the landscape test * Revert to LTS LXD
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* Disable network cut tests on arm * Back to LXD 5
* disable pgaudit during extensions changes * Bump libs
* Lock file maintenance Python dependencies * Fix linting --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Dragomir Penev <dragomir.penev@canonical.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* Make username mandatory * Second get password method * Default in get-password
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: GitHub Actions <41898282+github-actions[bot]@users.noreply.github.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 16/edge #936 +/- ##
========================================
Coverage 70.22% 70.22%
========================================
Files 16 16
Lines 3725 3725
Branches 542 542
========================================
Hits 2616 2616
Misses 974 974
Partials 135 135 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
taurus-forever
approved these changes
Jun 5, 2025
docs/how-to/deploy/multi-az.md
Outdated
| ## Set up GCE on Google Cloud | ||
|
|
||
| Let's deploy the [PostgreSQL Cluster on GKE (us-east4)](/t/11237) using all 3 zones there (`us-east4-a`, `us-east4-b`, `us-east4-c`) and make sure all pods always sits in the dedicated zones only. | ||
| Let's deploy the [PostgreSQL Cluster on GKE (us-east4)](https://discourse.charmhub.io/t/charmed-postgresql-k8s-how-to-deploy-on-gke/11237) using all 3 zones there (`us-east4-a`, `us-east4-b`, `us-east4-c`) and make sure all pods always sits in the dedicated zones only. |
There was a problem hiding this comment.
the url here sounds wrong.
There was a problem hiding this comment.
Because it leads to Discourse, or for another reason?
I've replaced it with the correct link to the K8s RTD site. There may still a few other Discourse links scattered around, but they will still work because the posts are still up.
Will fix and update all links after merging this.
marceloneppel
approved these changes
Jun 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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.
See main PR: Refactor v14 documentation for Sphinx
Issue
With the upcoming release of PG 16, documentation versioning is needed.
Solution
Introduce the Canonical Sphinx Starter Pack for compatibility with Read The Docs/Sphinx, and edit parts of the documentation only relevant to PostgreSQL 14.
Checklist