fix rule: fixed issue with alertmanager URL containing +#1582
fix rule: fixed issue with alertmanager URL containing +#1582GiedriusS merged 3 commits intothanos-io:masterfrom
Conversation
GiedriusS
left a comment
There was a problem hiding this comment.
The code looks very good to me and well tested 💪 however a philosophical question/idea: maybe it would be worth to error out if more than one + has been found in the parsedUrl.Scheme variable considering that none of the dns.QType variables have a +?
|
Thanks! Yes, good point. The function handles just parsing not validation. The validation is done in the resolver package so it eventually errors out afterwards (below example). This way the rule does not necessarily know all the resolvers types and who knows, maybe there will be some QType with Example: |
Ah, I haven't checked. Then it should be all good, thanks for the example output. |
bwplotka
left a comment
There was a problem hiding this comment.
Nice! Extremely small nit only =D then LGTM
Signed-off-by: Martin Chodur <m.chodur@seznam.cz>
Signed-off-by: Martin Chodur <m.chodur@seznam.cz>
Signed-off-by: Martin Chodur <m.chodur@seznam.cz>
437b5ec to
bc74f50
Compare
|
@bwplotka fixed and rebased, thanks for noticing :)) |
* fix rule: fixed issue with alertmanager URL containing + Signed-off-by: Martin Chodur <m.chodur@seznam.cz> * CR: updated changelog Signed-off-by: Martin Chodur <m.chodur@seznam.cz> * CR: add trailing period Signed-off-by: Martin Chodur <m.chodur@seznam.cz> Signed-off-by: Giedrius Statkevičius <giedriuswork@gmail.com>
fixes #1564
Changes
+which can be for example in credentialsVerification