-
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-580 Add notes re ms/mfe stack options, refine component gen ove… #594
Conversation
…rview, fix syncNext cmd
- The Entando blueprint includes scripts and tools to automatically generate a bundle ready for deployment to the ECR. The bundle will include your microservice, generated microfrontends, and any microfrontends that you have created manually under the `ui` folder | ||
- The generated Spring Boot microservice can be built and deployed to a Docker registry using the provided maven Jib plugin | ||
- Generated bundles can be pushed to a Git repository of the user's choice | ||
- The Entando Blueprint generates code compatible with the docker-based bundle project structure introduced in Entando 7.1. The bundle project will include a microservice, entity-level microfrontends, as well as other components you have added manually to the project. |
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.
...a microservice and entity-level micro frontends as well as other components that have been added manually
- The generated Spring Boot microservice can be built and deployed to a Docker registry using the provided maven Jib plugin | ||
- Generated bundles can be pushed to a Git repository of the user's choice | ||
- The Entando Blueprint generates code compatible with the docker-based bundle project structure introduced in Entando 7.1. The bundle project will include a microservice, entity-level microfrontends, as well as other components you have added manually to the project. | ||
- The generated Spring Boot microservice can be built and deployed to a Docker registry using the provided build structure |
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 reads like the build structure performs build and deploy... maybe rephrase to clarify how the build structure enables build/deploy
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.
Or drop the build structure phrase...
|
||
3. Deploy bundles to the [Local Hub](../compose/local-hub-overview.md) | ||
- Once your Docker images are pushed to your registry and your bundle is available in Git you can generate an Entando bundle descriptor and push the bundles to the ECR | ||
- The bundles can be versioned and updated using tags in the Git repository | ||
- Once your Docker images are pushed to your registry you can deploy the bundle to the Local Hub in an Entando Application |
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.
minor, but take the emphasis off of "you" to make instructions generalized and direct: "Once the Docker images are pushed to a registry, the bundle can be deploy to the Local Hub of an Entando Application"
- The Entando blueprint includes scripts and tools to automatically generate a bundle ready for deployment to the ECR. The bundle will include your microservice, generated microfrontends, and any microfrontends that you have created manually under the `ui` folder | ||
- The generated Spring Boot microservice can be built and deployed to a Docker registry using the provided maven Jib plugin | ||
- Generated bundles can be pushed to a Git repository of the user's choice | ||
- The Entando Blueprint generates code compatible with the docker-based bundle project structure introduced in Entando 7.1. The bundle project will include a microservice, entity-level microfrontends, as well as other components you have added manually to the project. |
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.
above comments apply to lines 33-38
…rview, fix syncNext cmd