Closed Trailingslashes closed 6 months ago
Wouldn't it be better if the filenames were aligned with what is provided by arista. I personally think the better approach is to just parse the filename out of the provided url attribute. Thoughts?
I guess my thinking was to read the url in the definition and reconstruct the name of the file based on that. When I read a file on /mnt/flash, I want to know if it's a 32 or 64 bit file right away. I don't want to rely on the md5sum. But yes, you're right, following Arista's standard - if there is no 64bit in the name, we can assume it's 32 bit right away.
I suppose that's what issue #313 is trying to do. I did this to guarantee that I'm copying files correctly.
I'm baffled by the fact, this script assembles the destination filename from the version variable. I suspect this was done from a uniformity perspective. Alternatively it was done like this before 'EOS64' images became available and it was a non-issue at the time. However in the networking world, ztp/automation aside, we almost always use the filename set by the vendor. In fact, I don't think I have ever deviated from the vendor filenames. I think parsing the url variable is the most elegant solution here. It also appeals to the intuition of most network engineers.
I'm not sure what to do here as I'm not super familiar with github etiquette. Do we collaborate or should I put in a competing pull request? Hopefully that didn't sound snarky, I assure you there is no snark present :-)
You're more than welcome to create your own pull request.
Closing as #406 implements similar functionality
Images labelled with 32 or 64 should be copied on /mnt/flash with the correct name.
show version:
see #404