Open plajjan opened 10 years ago
I'd like to avoid introducing a dependency on a module that is not available in Debian, so perhaps it's best to avoid excel altogether.
Have you already thought about implementing it in the nipap cli instead of the web-ui? I feel like it would be better off there.
My thinking was that whoever wants an excel file is also more likely to use the Web UI.
Nothing stops us from adding it in both places though...
Well the use-cases I could think of are a) changing to a different ip management tool b) to do some form of analysis
In my mind both is something that is done rarely and probably by the server administrator. I was just thinking of keeping the web-ui as clean and simple as possible without adding some knick-knack :)
This is not all at what I have in mind. Our primary use case is exporting information into a "neutral" format (if you could call Excel that) so that we can hand over information to vendor and partners. It is pretty common for us to buy a system from vendor X and in the dialogue between us and the vendor we transfer information in the form of Excel files. An export to excel feature would ease this work.
For the use case of changing to another IPAM, you could dump from the database or whatever. It is not really something I tend on writing a tool for doing.
For analysis, I think the export to excel in the web UI will work fine, or the export-csv.py that is already in utilities/ would work.
With that said, once having written the actual code that writes an Excel file, it's probably not much work making it available via CLI.
Implement export functionality so that user can download a csv or excel file.
I'm not sure what modules for excel file exports work well so maybe we should stick to csv for now. There's really no extra functionality with Excel format that we need.
Output could be an entire VRF or perhaps filtered by the current search query.