-
Notifications
You must be signed in to change notification settings - Fork 26
[MISC] Sync main to 16/edge #1212
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
base: 16/edge
Are you sure you want to change the base?
Conversation
* 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>
* Handle empty region * Handle invalid stanza name
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
D-p-w v32+ requires refresh v3 versioning, otherwise: https://github.com/canonical/postgresql-operator/actions/runs/17777132580 > Invalid workflow file: .github/workflows/promote.yaml#L28 > error parsing called workflow ".github/workflows/promote.yaml" -> > "canonical/data-platform-workflows/.github/workflows/_promote_charm.yaml@v35.0.2": > failed to fetch workflow: workflow was not found.
* Use Patroni API for is_restart_pending * Cached props * Magic sleep and legacy rel names * Hash config value and restart only on change * Tweaks * Legacy interface fix * Fix legacy test * Increase idle period * Wrong username * Remove copypasta
* Refactor charm version explanation pages * refactor releases reference pages * Move all legacy information to legacy charm page * Add feature lists back to modern charm versions page * fix broken references
* Volume tests * Manually deploying
* DPE-8337 Disable Patroni config to prevent possible dataloose Disable Patroni config options explecitely: remove_data_directory_on_rewind_failure and remove_data_directory_on_diverged_timelines. P.S. they are disabled by default in Patroni. * DPE-8337 Fix integration tests * Force set the rewind config --------- Co-authored-by: Dragomir Penev <dragomir.penev@canonical.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…ss roles (#1186) * Mute error message to debug * Create access roles * Move setup of access roles to upgrade granted * Try to use mnt for storage * Skip disk cleanup
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* Set strict sync mode * Try bootstrapping with false strict mode * Move increase writes check * Try to cleanup only if the test didn't fail * Add checks for strict mode * Revert "Add checks for strict mode" This reverts commit 85b7f61. * Try using env to detect test failure * Remove redundant arg * Try stopping instead of cleaning * Only set strict mode if there are multiple active units * Check sync units as well
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* Remove old revision of secret Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com> * Remove secrets' old revision on upgrade Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com> * Remove all previous secret revisions Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com> * Handle juju/juju#20782 Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com> * Revert "Handle juju/juju#20782" This reverts commit 0e29e0e. Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com> * Reapply "Handle juju/juju#20782" This reverts commit 0e23c96. Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com> * Handle juju/juju#20794 Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com> * Consider all secrets created by the charm Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com> * Check for secrets support Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com> * Remove upgrade logic Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com> --------- Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>
Issue: Some tests start failing ops v3 (especially self-healing). It requires investigation, but 14/stable is long waited for PS6 fixes. Solution: Temporary reverting ops to previous version 2 to release the next 14/stable
Codecov Report❌ Patch coverage is
❌ Your project check has failed because the head coverage (66.94%) is below the target coverage (70.00%). You can increase the head coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## 16/edge #1212 +/- ##
===========================================
+ Coverage 64.57% 66.94% +2.37%
===========================================
Files 17 17
Lines 4344 4347 +3
Branches 671 671
===========================================
+ Hits 2805 2910 +105
+ Misses 1357 1242 -115
- Partials 182 195 +13 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Sync changes from main to 16/edge
Checklist