Morten Brekkevold

Actually, what is needed is a new (or an update to an existing) report in the report system. All reports can already be exported to CSV. I have followed up...

Adding a discussion label here, due to lack of feedback. NAV already exports to CSV, which can be directly opened in Excel. If this is a a specific report needed...

A SQL report of "vendor, serial number, 'device type'" for all operational devices might be enough here, it seems. This can be exported as CSV and used for the stated...

The spec here was horribly lacking. At some point I tried to build a report in cooperation with one representative of the NAV reference committee, but I never got complete...

I could add that whenever you see pylint disables like ```python # pylint: disable=W0611 ``` This is the same thing. Pylint's W0611 is equivalent to ruff's F401

> I forget if we remembered to add an issue for future TLS verification, but I'm putting it on my TODO since I have to run to a meeting in...

This is still a WIP. The biggest obstacle currently seems to be that it is really tricky to make PostgreSQL setup as a fixture to work properly because of Django:...

I might also add that this could prove quite difficult for interface counter data, given how they are currently stored by NAV. In the RRD days, what NAV would actually...

> From `The formatting system is disabled by default. To enable it, it’s necessary to set USE_L10N = True in your settings file.` to `The formatting system is enabled by...

> In meantime this PR will remain in kind of frozen state because SIKT has no current need or time to work on it? Sounds about right for the time...