Open
Conversation
Author
|
I checked the ContainerSource and it has |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DO NOT MERGE
I think I've managed to get the AMQP EventSouce to work. Some notes/comments.
In the logs I see some empty CloudEvents so I assume there are some empty AMQP messages being delivered.
adaptorimage to DockerHub to get it to deploy. I'm not sure why but simply tagging it locally didn't want to work. I suspect theContainerSourcemay have a property ofImagePullPolicy: Alwayswhich will only work, I think, with images in a remote repo.oc new-app --name=artemis vromero/activemq-artemis -e RESTORE_CONFIGURATION=true/samples' which I used withoc apply -f` to bring everything up