Integrate Scraparr in Servarr as dependency#62
Conversation
|
@imgios I have added api_version ( with default value v3 ) for scraparr. Should the helm chart support this in the future in case someone wants to change it? |
This is an optional value, having it there is perfectly fine and future proof in my opinion. |
imgios
left a comment
There was a problem hiding this comment.
@mrgionsi thanks for the contribution, it looks good so far!
I think we need to do some magic tricks to get the default values for the services URL param (e.g. servarr service name directly in scraparr configuration). As a result of your changes, the user is now required to manually fill in the URL values, which is not really the aim of servarr. Not sure if we want to include these changes in this PR or merge this and perform this development on another PR.
@fonzdm what's your POV here?
Thanks mate. @fonzdm Can you please test it and in case approve pr? |
I'm sorry, did you even try something before creating a PR??? |
|
Joking, I will try asap 😁 |
scraparr-1.1.0 has initContainers , which comes in handy with servarr, cause otherwise scraparr will be deployed beforehand and won't be able to reach any *arr service.
Thanks for your valuable feedback. |
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature: Introduce scraparr as subchart
What is the current behavior? (You can also link to an open issue here)
There is no mechanism for exporting metrics for servarr
What is the new behavior (if this is a feature change)?
Scarparr is introducing metrics to be used in prometheus.
Closes #55