update the conditions to create beans based on eventPortal section #128
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.
What is the purpose of this change?
Update the conditions to create the spring beans based on the existence of the
eventPortal
section in theapplication.yml
fileHow was this change implemented?
By providing default values for the
EventPortalProperties
when theeventPortal
doesn't exist in theapplication.yml
file. Also, updating the conditions to instantiate classes based on the value ofstandalone
flag.How was this change tested?
Manually by starting the EMA using different configs in
application.yml
file, e.g., with and withouteventPortal
section, then running scans in online and offline modesIs there anything the reviewers should focus on/be aware of?
N/A