Skip to content
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

deploy_packages should check the AEM healthiness after all packages were deployed #75

Open
mbloch1986 opened this issue Oct 15, 2019 · 1 comment

Comments

@mbloch1986
Copy link
Contributor

The deploy_packages manifest is checking the AEM healthiness after each package installation.

Instead of checking the AEM healthiness after each apckage we should should check it after all packages of the hashs are installed and not after each package installation.

In a scenario where one package in the deployment descriptor brakes the bundle dependency of an existing installed bundle as it was not updated yet, the healthcheck fails. The package installation will still go ahead and update the bundle later during the deployment process and will solve the dependency error therefore AEM is healthy at the end of the deployment process.

@mbloch1986 mbloch1986 changed the title deploy_packages should check the AEM healthiness after all packges were deployed deploy_packages should check the AEM healthiness after all packages were deployed Oct 15, 2019
mbloch1986 added a commit to mbloch1986/puppet-aem-resources that referenced this issue Nov 14, 2019
### Changed
- Change Package Deployment process to check AEM Healthy after all packages were deployed shinesolutions#75
- Update default parameters for AEM Health checks after all packages were deployed shinesolutions#76
cliffano pushed a commit that referenced this issue Nov 15, 2019
* Change Package deployment process #75 #76

### Changed
- Change Package Deployment process to check AEM Healthy after all packages were deployed #75
- Update default parameters for AEM Health checks after all packages were deployed #76

* Minor changelog clarification
@mbloch1986
Copy link
Contributor Author

To realise this we need to refactor the whole manifest deploy_packages and replace it with a new module deploy_packages.

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

No branches or pull requests

1 participant