Skip to content
This repository has been archived by the owner on May 6, 2021. It is now read-only.

Set viper config to our own, or this will crash #19

Merged
merged 3 commits into from
Oct 11, 2018
Merged

Set viper config to our own, or this will crash #19

merged 3 commits into from
Oct 11, 2018

Conversation

chmouel
Copy link
Contributor

@chmouel chmouel commented Oct 10, 2018

@codecov
Copy link

codecov bot commented Oct 10, 2018

Codecov Report

Merging #19 into master will decrease coverage by 1.48%.
The diff coverage is 25%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #19      +/-   ##
==========================================
- Coverage   28.03%   26.55%   -1.49%     
==========================================
  Files           4        4              
  Lines         321      354      +33     
==========================================
+ Hits           90       94       +4     
- Misses        219      248      +29     
  Partials       12       12
Impacted Files Coverage Δ
configuration/configuration.go 58.06% <25%> (-25.27%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e5ee5a9...59040f4. Read the comment docs.

Binary was not running due of bad usage of composition between common
class. After chatting with the -common people, it seems that configuration from
common is getting removed, so let's instead use our own and only pickup the
stuff we need to run the service + db.
@chmouel chmouel merged commit b44524f into fabric8-services:master Oct 11, 2018
@chmouel chmouel deleted the fix-configuration-comp branch November 27, 2018 15:56
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant