Skip to content

Added release notes for Private cloud portal release 7.27.0#10952

Open
mxashokkhedkar wants to merge 3 commits intomendix:developmentfrom
mxashokkhedkar:portuns_release_7_27_0
Open

Added release notes for Private cloud portal release 7.27.0#10952
mxashokkhedkar wants to merge 3 commits intomendix:developmentfrom
mxashokkhedkar:portuns_release_7_27_0

Conversation

@mxashokkhedkar
Copy link
Copy Markdown
Contributor

No description provided.

@CLAassistant
Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@MarkvanMents
Copy link
Copy Markdown
Collaborator

@mxashokkhedkar
Could you please sign the CLA? Not strictly necessary for Mendix contributors, but it makes our life easier if PRs pass all the checks. Thanks.
image

Copy link
Copy Markdown
Collaborator

@MarkvanMents MarkvanMents left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.
I just have one question for clarification - can you look at this and also sign the CLA.
Thanks.

PS, I notice that you had to update .claude/settings.json. This is something we hadn't thought about. Can you suggest how we can avoid this in future?

* We have introduced configurable heap memory to align with Public Cloud optimization logic as a default for Operator 2.26.0 and newer.
* We have aligned resource plans with Public Cloud standards and continue to support legacy plans.
* We have moved the Mendix on Azure information banner to the Cluster Manager homepage.
* Cross-cluster restores are not supported. Environments are visible only within the same cluster.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this actually new in this release, or are we stating something which has always been the case?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We had this already, but it was showing environments across the different clusters and if the customer selects environments from different clusters while restoring backup was problematic in some cases so we blocked that now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants