-
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
condition start method on bucketprocessor #2551
condition start method on bucketprocessor #2551
Conversation
Hello benzekrimaha,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
@@ -451,19 +451,24 @@ class LifecycleBucketProcessor { | |||
start(done) { | |||
this.clientManager.initSTSConfig(); | |||
this.clientManager.initCredentialsManager(); | |||
async.series([ | |||
const tasks = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to take this out of the async.series
, you can just call done()
when this._mongoConfig
is not configured.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files
... and 4 files with indirect coverage changes
@@ Coverage Diff @@
## development/8.7 #2551 +/- ##
===================================================
+ Coverage 69.44% 69.56% +0.12%
===================================================
Files 194 194
Lines 12792 12794 +2
===================================================
+ Hits 8883 8900 +17
+ Misses 3899 3884 -15
Partials 10 10
Flags with carried forward coverage won't be shown. Click here to find out more. |
ff91dec
to
7a5e390
Compare
7a5e390
to
8dfabc7
Compare
/approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
this._resumeServiceForLocation.bind(this), | ||
this._log); | ||
this._locationStatusStream.start(done); | ||
if (this._mongoConfig) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
note: eventually (once we support pause/resume on s3c), we will need to have an abstraction here, and always create some sort of "locationStatusStream" : listening to mongo (as today in zenko) or to something else (maybe zookeeper?)
but indeed we don't have this now, this will be done later.
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue BB-549. Goodbye benzekrimaha. |
Issue : BB-549