Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upRemove config dependency in discovery #3013
Comments
This comment has been minimized.
This comment has been minimized.
|
Are there not more dependencies here? The import option seems to make more sense to me, if we have the Is there anything I'm missing here? |
gouthamve
added
the
hacktoberfest
label
Sep 28, 2017
This comment has been minimized.
This comment has been minimized.
|
I'll pick this up! |
This comment has been minimized.
This comment has been minimized.
|
@shubheksha I have done some work around discovery and config recently so ping me on IRC (prometheus-dev) if you need any pointers. |
This comment has been minimized.
This comment has been minimized.
|
@fabxc, as part of this change, will the SD structs be moved to their respective packages as implied by the title as well? Or are we only concerning ourselves with |
This comment has been minimized.
This comment has been minimized.
|
@shubheksha I don't think there is a definitive answer here. I think @brian-brazil can also share some more context here. |
This comment has been minimized.
This comment has been minimized.
|
@krasi-georgiev But at least the issue title implies getting rid of the SD->config dependency, which would naturally have to include moving any SD-related config structs to the SD packages as well. |
This comment has been minimized.
This comment has been minimized.
|
Yes I agree with this as well. Just have some faint memory that there were at least 2 opinions on this. |
This comment has been minimized.
This comment has been minimized.
|
I don't recall any disagreements here. Ultimately if we want SD to be usable as a separate component then the config bits need to move out of the config package. |
This comment has been minimized.
This comment has been minimized.
|
Yea, moving them to the respective packages is a good first step. |
shubheksha
referenced this issue
Dec 27, 2017
Merged
Refactor SD configuration to remove `config` dependency #3629
juliusv
closed this
in
#3629
Dec 29, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
fabxc commentedAug 1, 2017
Currently the discovery packages relies on
configviaconfig.TargetGroup. This is not the best design for reusability and the type should be moved into the package itself.To be discussed whether we just have the type twice and map between it or import
discoveryintoconfig.