Deployment issue #818
Open
Deployment issue #818
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
* updatedcltwo_final * updatedcltwo_final_consistency
* updatedcltwo_final * updatedcltwo_final_consistency * snapshot_update
ReddyAnand-BV
temporarily deployed
to
github-pages
* Added document_id as env variable * Test changes * branch admin -prepare release emodb-6.5.134 * branch admin -prepare for next development iteration --------- Co-authored-by: abhyudaya-mohanty_bveng <[email protected]> Co-authored-by: jenkins <[email protected]>
…quisite (#829) * feat: integrate sqs to blob service * Create an sqs service to send messages to sqs * Send all the incoming PUT and DELETE request to sqs * feat: inlcude functionality to store encoded blob in sqs * Convert the incoming blob to bytearray, encode it and send it to sqs * Handle the incoming api request of PUT blob object * Send the attributes and object to sqs * feat: restructure the queue intialization following better architecture * Create interface for queue, so can include multiple implementations * Follow lose coupling * Use a factory method for sqs initialization * PD-239427 fix: fix logging and simplified factory * feat: include params required for iss, send to sqs and update queue name * Include queue url param to be sent to sqs * Update the queue name * Update the factory as per the required changes * update: update tags for deployment * branch admin -prepare release emodb-6.5.135 * branch admin -prepare for next development iteration * update: add fifo queue for blobstore migration and tag changes * branch admin -prepare release emodb-6.5.144 * branch admin -prepare for next development iteration * fix: remove sending of bytecode to sqs * For large files , bytecode is too huge to be sent to sqs * Send request url instead of bytecode * feat: add custom exceptions * handle exceptions in a robust way * add digestbytes to sqs * chore: add tags skip sonatype for deployment * branch admin -prepare release emodb-6.5.159 * branch admin -prepare for next development iteration * fix: add back sonatype dependency * branch admin -prepare release emodb-6.5.160 * branch admin -prepare for next development iteration * Removed bytearray in sqs put * Update MessagingService.java for removing byte * Update SQSService.java * branch admin -prepare release emodb-6.5.161 * branch admin -prepare for next development iteration * skipping nexus plugin for testing --parent.pom * branch admin -prepare release emodb-6.5.162 * branch admin -prepare for next development iteration * add metrics to Queue poll * branch admin -prepare release emodb-6.5.163 * branch admin -prepare for next development iteration * update pom version * branch admin -prepare release emodb-6.5.165 * branch admin -prepare for next development iteration * branch admin -prepare release emodb-6.5.166 * branch admin -prepare for next development iteration * feat: add poll metrics for dedupq * feat: add send count metrics * fix: add metrics for sendBatch * udate: update tags from 167 to 168 * fix: fix the compilation issue remove metricregistry from constructor * branch admin -prepare release emodb-6.5.168 * branch admin -prepare for next development iteration * chore: update tags from 168 to 169 * branch admin -prepare release emodb-6.5.169 * branch admin -prepare for next development iteration * fix: fix the metric tag name issue * branch admin -prepare release emodb-6.5.170 * branch admin -prepare for next development iteration --------- Co-authored-by: jenkins <[email protected]> Co-authored-by: anandujayan <[email protected]> Co-authored-by: ReddyAnand-BV <[email protected]> Co-authored-by: Nabajyoti Dash <[email protected]>
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.
Github Issue
1234
What Are We Doing Here?
Here is where you should describe the problem you are solving as it relates to the Github Issue referred above, adding any fine
details on the solution that might otherwise not be recognizable for someone
unfamiliar with the changes. Add some pictures if it helps.
How to Test and Verify
Risk
Level
Low,Medium, orHigh. Give an indication of what you think is the level of change introduced by this PR.Highmeans a massive change to a core functionality.Lowmeans a really minor change that shouldn't have any regression effect.Required Testing
Smoke,Regression, orManual. (All changes except documentation need smoketesting at a minimum).
Risk Summary
Add one or a few complete sentences about the possible risks or concerns for
this change.
Code Review Checklist
Tests are included. If not, make sure you leave us a line or two for the reason.
Pulled down the PR and performed verification of at least being able to
build and run.
Well documented, including updates to any necessary markdown files. When
we inevitably come back to this code it will only take hours to figure out, not
days.
Consistent/Clear/Thoughtful? We are better with this code. We also aren't
a victim of rampaging consistency, and should be using this course of action.
We don't have coding standards out yet for this project, so please make sure to address any feedback regarding STYLE so the codebase remains consistent.
PR has a valid summary, and a good description.