-
Notifications
You must be signed in to change notification settings - Fork 24
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
ENDOC-566 bundle details page #569
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a start, I'm guessing I'll have more ideas on the next round. Apologies in advance.
@@ -5,7 +5,7 @@ When generating a microservice using the Entando Component Generator there are a | |||
* Microservice code | |||
* The Component Generator currently only supports the generation of Spring Boot microservices but will support the generation of Quarkus based services soon. | |||
* If you're interested in using Quarkus in your Entando app, contact us on the [Forum](https://forum.entando.org/) or [Community Slack](https://join.slack.com/t/entandocommunity/shared_invite/zt-g609owdv-2K~YRh8zrI6lqlWo4aFWUw) and we'll help you get started. | |||
* If you're considering non-Java based microservices, [here is a definition of an Entando plugin](../curate/bundle-details.md#plugin), including information on the runtime contract required to use them. | |||
* If you're considering non-Java based microservices, [here is a definition of an Entando plugin](../curate/bundle-details.md#microservices-specifications), including information on the runtime contract required to use them. | |||
* Database type | |||
* Entando recommends standardizing your choice of database to simplify operational maintenance but you do have the ability to use different databases for different microservices if you choose. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
omit "if you choose" (redundant and sentence is already quite long without punctuation to break it up)
@@ -5,7 +5,7 @@ When generating a microservice using the Entando Component Generator there are a | |||
* Microservice code | |||
* The Component Generator currently only supports the generation of Spring Boot microservices but will support the generation of Quarkus based services soon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this true? should we either put a date/rev for when to expect this or kill it to not make vague promises?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's drop the quarkus statement. We've been saying that for years.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bypassing all comments for this document. This document needs an update in general but with so much to finish for 7.1, I have to prioritize
@@ -5,7 +5,7 @@ When generating a microservice using the Entando Component Generator there are a | |||
* Microservice code | |||
* The Component Generator currently only supports the generation of Spring Boot microservices but will support the generation of Quarkus based services soon. | |||
* If you're interested in using Quarkus in your Entando app, contact us on the [Forum](https://forum.entando.org/) or [Community Slack](https://join.slack.com/t/entandocommunity/shared_invite/zt-g609owdv-2K~YRh8zrI6lqlWo4aFWUw) and we'll help you get started. | |||
* If you're considering non-Java based microservices, [here is a definition of an Entando plugin](../curate/bundle-details.md#plugin), including information on the runtime contract required to use them. | |||
* If you're considering non-Java based microservices, [here is a definition of an Entando plugin](../curate/bundle-details.md#microservices-specifications), including information on the runtime contract required to use them. | |||
* Database type | |||
* Entando recommends standardizing your choice of database to simplify operational maintenance but you do have the ability to use different databases for different microservices if you choose. | |||
* Supported choices are none, MySQL, and Postgres. Enterprise customers can choose Oracle but should contact Entando Support for details. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is "Entando Support" a thing? should we link this to the appropriate contact section?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd leave it as-is. It's a common term and if they have a subscription they should know how.
@@ -20,7 +20,7 @@ For specifications on docker-based bundles, see the [Bundle Details](bundle-deta | |||
|`descriptorVersion`| v1| v5 | |||
| Bundle Specifications |Defined with descriptor files | Built with [ent bundle CLI](../getting-started/ent-bundle.md) tool |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Defined by
Built with the Entando Bundle CLI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
trying to keep this column as short as possible. so not including every article in the fragments. I don't think it takes anything away from understanding
left with as is, doesn't change meaning
|`deploymentBaseName`|String|No||Used for defining custom pod names| | ||
|`roles`|String[]|No||Exposed security roles| | ||
|`env`|[EnvironmentVariable[]](#environment-variables-specification)|No||Required environment variables| | ||
|`commands`|Command[]|No||Custom commands definitions| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
command (not plural)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it can be plural, added parenthesis
|`dbms`|Enum|No|*none *embedded *postgresql *mysql *oracle|DBMS required by the MS to provide services| | ||
|`ingressPath`|String|No||Custom ingress path| | ||
|`healthCheckPath`|String|No||Endpoint for a health check| | ||
|`deploymentBaseName`|String|No||Used for defining custom pod names| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
used to define
|Name|Type|Required|Possible Value|Description| | ||
|:-|:-|:-|:-|:------------------------| | ||
|`name`|String|Yes||Name| | ||
|`type`|Enum|Yes|*internal *external| Kind of claim with reference to bundle | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"type of" instead of "kind of" ("kind of" reads like "sort of")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought that too but using the same word to describe the thing you're describing is not recommended. reworded
|:-|:-|:-|:-|:------------------------| | ||
|`name`|String|Yes||Name| | ||
|`type`|Enum|Yes|*internal *external| Kind of claim with reference to bundle | | ||
|`serviceName`|String|Yes||Microservice name into the bundle| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
name into the bundle? that's confusing ??
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
noticed that too, but it came from Notion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Notion is confusing. I'm changing it.
pages/ | ||
svc/ <= auxiliary services | ||
keycloak.yml | ||
svc/ <= auxiliary services for local development |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Lyd1aCla1r3 correct, it's only for local work
"commands": { "build": "custom-command" } | ||
} | ||
``` | ||
#### mfeConfig Specifications |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something is wrong here. mfeConfig isn't a thing. configMfe is a string indicating the custom element for the corresponding config MFE. And what is listed in the mfeConfig section below should just be inline in the microfrontend section. You cannot have an array of mfeConfig containing params, contextParams, systemParams, you can just have the actual params, contextParams, and systemParams under the microfrontend.
} | ||
}, | ||
"contextParams": { | ||
"page_code": "${page_code}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to remove all of the ${page_code] bits here in lines 186-188. I think that was pseudo-code used by Engineering to indicate their implementation. The actual working code (although I'm setting up to test it) doesn't include values. See https://github.com/entando/entando-showcase-bundle/blob/master/entando.json for a real example.
@Lyd1aCla1r3 lots of changes in second commit so will need to look there