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 up`promtool update rules` discards comments #3475
Comments
This comment has been minimized.
This comment has been minimized.
|
This is a limitation of the YAML libraries available in Go, I'm afraid there's not much we can do about this. |
This comment has been minimized.
This comment has been minimized.
There's little to no reason (value escaping?) to use libraries for content generation, and since the output is pretty flat, it might as well be generated by hand. But even then you'd need to hack parser to allow it to output comments in some form. (That being said, I'm not sure if this issue affects a lot of people and is therefore worth the effort, but here it is.) |
This comment has been minimized.
This comment has been minimized.
|
Unless you can find a Golang yaml library that supports comments, there's nothing we can do here. |
brian-brazil
closed this
Dec 1, 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. |
vthriller commentedNov 14, 2017
What did you do?
promtool update rules rulefileWhat did you expect to see?
Given the following
rulefile:I expected to see the output silimlar to this:
(or
#or quuxto be on the same level aslabels:or whatever)What did you see instead? Under which circumstances?
Environment
System information: (irrelevant)
Prometheus version:
Alertmanager version: (irrelevant)
Prometheus configuration file: (irrelevant)
Alertmanager configuration file: (irrelevant)
Logs: (none)