-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add tests for AEM keystore #95
Comments
Extend component test to verify AEM Keystore contains the imported key shinesolutions#95
The |
Extend component test to verify AEM Keystore contains the imported key shinesolutions#95
Check is not included yet, as the check is failing while baking with packer-aem
|
Once the issue is solved we need to add this check for the repo aem-aws-stack-provisioner for the reconfiguration scenario |
In order to check for the error message we probably should add the following check to the inspec test: its('stderr') { should eq '' } |
Error message: �[0;32m aws: �[38;5;208m ∅ stdout should eq ""�[0m |
Error persist even changing the order of the keytool option doesn't help:
Or adding
|
Now that the keystore password is stored in parameter store, we need to first retrieve the password (ARN would be available from user config YAML) before using it for testing. |
The problem we encountered before where the keystore couldn't be found for testing must have been something to do that the content of Therefore we have use the new path to the aem keystore e.g. as done for this test here #174 Additional we can't test the keystore password with the current implementation of how we retrieve the hiera parameter in our inspec tests, as the SSM parameter store lookup only works with hiera 5 while the hiera lookup in our InSpec tests only supports hiera 3. |
the aem keystore is located at
/opt/aem/{author/publish}/crx-quickstart/ssl/aem.ks
We need to verify that the key has been added to the keystore with the alias
cqse
The above command should work but was returning an exit status of 1.
The text was updated successfully, but these errors were encountered: