This is an automated email from the ASF dual-hosted git repository. dahn pushed a change to branch healthcheck-main in repository https://gitbox.apache.org/repos/asf/cloudstack.git
discard 7dfa32a859b Merge branch 'main' of https://github.com/apache/cloudstack into healthcheck-main discard 162482dc243 Merge branch 'main' of https://github.com/apache/cloudstack into healthcheck-main discard 0896f32446e Merge branch 'healthcheck-main' of https://github.com/apache/cloudstack into healthcheck-main discard 0869f00095f 4.20/main Health Check, please don't merge this! discard c19fc1bb3f0 Merge branch 'main' of https://github.com/apache/cloudstack into healthcheck-main discard fb49fd42d89 Merge branch 'main' into healthcheck-main discard 477820a15df 4.20/main Health Check, please don't merge this! add 28e24111100 engine-schema: fix naming for AlmaLinux (#11011) add 675ee2ab398 Add parameter to not create additional users on `cloudstack-setup-databases` (#9969) add 49e1392f348 4.20/main Health Check, please don't merge this! This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (7dfa32a859b) \ N -- N -- N refs/heads/healthcheck-main (49e1392f348) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: .../resources/META-INF/db/schema-42010to42100.sql | 6 +++--- setup/bindir/cloud-setup-databases.in | 21 +++++++++++++++++++++ 2 files changed, 24 insertions(+), 3 deletions(-)
