ENDOC-551 7.1 release notes #553
Conversation
Lyd1aCla1r3
commented
Aug 23, 2022
Lyd1aCla1r3
commented
- current as of 2022-08-22 7PM PST
- WIP
- all bolded terms/phrasing in question
| ### Compatibility | ||
|
|
||
| **check** | ||
| * [Entando 7.1 Compatibility](https://entando.com/entando-de-app/cmsresources/cms/documents/Entando_7.0_Compatibility.pdf) |
There was a problem hiding this comment.
Add a note somewhere that we need to point this to 7.1 when we have it?
| - Security fixes | ||
| - Node-based CLI module to manage bundle projects | ||
| - Decoupled MFE ⇒ MS communication via service discovery ([API claims](../getting-started/ent-api.md)) | ||
| - New docker-based bundles (bundles entirely distributed via Docker/OCI images) |
There was a problem hiding this comment.
not a big deal but it's not actually distributed via Docker and OCI images? OCI images are distributed by docker?
There was a problem hiding this comment.
Docker image is synonymous with OCI image. I think this language works.
| - Decoupled MFE ⇒ MS communication via service discovery ([API claims](../getting-started/ent-api.md)) | ||
| - New docker-based bundles (bundles entirely distributed via Docker/OCI images) | ||
| - App Builder is now extensible through bundles (supports override of core App Builder components and the addition of EPC extensions) | ||
| - App Builder main menu is converted to a overridable bundle containing an MFE and BFF service |
| - Fixed CVE-2022-33879 (apache tika, DoS) | ||
| - Fixed CVE-2022-24823 (apache netty, Information Exposure) | ||
|
|
||
| ### **AdminConsole:** |
There was a problem hiding this comment.
is there a reason why this is bolded with a colon?
There was a problem hiding this comment.
yes lol i wanted to confirm it should be "Admin Console" but missed it during our triage
There was a problem hiding this comment.
Lose this section, combine with App Builder.
| - Fixed the clone function for UX fragments | ||
| - Minor adjustments to support docker-based bundles | ||
| - Minor fixes related to pagination and usability | ||
| - Invoking APIs now sends the authentication header (instead of explicitly sending authentication cookies) |
There was a problem hiding this comment.
parenthesis not needed here
|
|
||
| ### Entando CLI (ent) | ||
|
|
||
| - Dropped support for Entando <= 6.3.0 and Kubernetes <= 1.18 |
There was a problem hiding this comment.
Maybe I'm missing something, what does this mean? those arrows confuse things
There was a problem hiding this comment.
Less than or equal to 6.3.0, etc. Math-y.
There was a problem hiding this comment.
Hah, good idea. Correction, old-school-developer-math-y. ;)
| - Added shortcuts for running internal k9s, crane, jq and fzf (e.g. `ent crane`) | ||
| - `ent attach-kubectx` now supports `--current` to attach the current kubectl context (e.g. following an `oc login`) | ||
| - Modified `get-bundle-id` to support docker-based bundles | ||
| - Fixes to `ent help` and logging |
There was a problem hiding this comment.
logging is strange without an object>> logging management? (from below)
There was a problem hiding this comment.
? logging works well by itself. logging is a thing.
|
|
||
| - New CLI module "ent bundle" to manage docker-based bundles | ||
| - Support for the following workflows: | ||
| - From scratch: User can create a new bundle project and then add components from existing projects or using external tools |
There was a problem hiding this comment.
using external tools >> use external
to match add components and use external...
There was a problem hiding this comment.
disagree. it reads "add components...using external tools"
| - Capability to customize the build, run and packaging commands | ||
| - Custom resource descriptor generation for the current bundle and external Docker repositories | ||
| - Improved log management during parallel builds | ||
| - Improved local testing capabilities and auxiliary services management based on docker-compose |
There was a problem hiding this comment.
to clarify, when is it docker-compose?
| - File structure deployed to AppEngine is redesigned with improved scoping | ||
| - Added new MFE widget capabilities: | ||
| - Support for service discovery driven by the [API claims mechanism](../getting-started/ent-api.md) | ||
| - Automatic generation of the widget configUi |
There was a problem hiding this comment.
@nshaw how is this formatted in code?
There was a problem hiding this comment.
There was a problem hiding this comment.
"Automatic generation of the widget configUi integration code"
| - Improvements to EntandoPlugin ingress management: | ||
| - Canonical ingress path: Determined by the infrastructure and used extensively, from internal communication to service discovery | ||
| - Customized ingress path: An alternative path that can be used by 3rd parties | ||
| - Retrocompatible changes to the EntandoPlugin CRD to store both the customized and canonical paths |
There was a problem hiding this comment.
Can we use Backward compatible here? More common usage
| ### **AdminConsole:** | ||
|
|
||
| - Improved handling of special chars in page titles | ||
| - Improved visual and functional integration with new AppBuilder EPC menu |
There was a problem hiding this comment.
Lose this line, internal implementation detail.
