database-monitoring: production updater default 0.1.12 (0.3.1) - #131
Merged
Merged
Conversation
The 0.1.10 updater is refused by Cloudflare (403, error 1010) and never checks in. Merge after agent-v0.1.11 is published. Closes #130
amandeepsingh-99
approved these changes
Oct 3, 2026
greg-aligiannis
approved these changes
Oct 3, 2026
anchoo2kewl
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #130.
Module 0.3.0's production default updater image
…/elastio/elastio-database-monitoring-updater:0.1.10is refused by Cloudflare (403, error 1010) and never checks in, so productionupdater = truedoes nothing (elastio/database-monitoring-agent#24, fixed by #25; release in elastio/database-monitoring-agent#27).updater.tf: production default →0.1.12; development default unchanged (:latest, already fixed).terraform test27/27..module.toml0.3.0 → 0.3.1.Merge only after
agent-v0.1.12(published and signed 2026-10-03, run 37145009089) (the image must exist), then run thereleaseworkflow to publish 0.3.1.