[JAMES-3767] rename pulsar artifact #1008
Merged
Conversation
This file contains 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
This commit also adds a minimal README.md to be improved with more detailed deployment instructions in the future.
chibenwa
approved these changes
May 20, 2022
|
My guess is flaky test ... |
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.
Hello,
I renamed the artifact as discussed by email, I also added an bit of readme.
Contrary to what we wrote in the mail, I decided to remain on an SQL store for domains, recipient rewrite tables and users. The reason is that while relying on files would be enough for our specific use case, it would also seriously limit the
scalingpart of the artifact.