Why I did it Arista did not update db with eeprom info. Previous PR had issues that were reverted. How I did it Had Arista eeprom class inherit the class that has method to update db. Updated platform API methods for Arista 202012. How to verify it In redis-cli the keys and values can be seen. Can use sonic-mgmt testing to verify behavior, and see the chassis platform API methods have not regressed. |
||
---|---|---|
.. | ||
bfn-modules | ||
docker-saiserver-bfn | ||
docker-syncd-bfn | ||
docker-syncd-bfn-rpc | ||
sonic-platform-modules-arista@361707e1ae | ||
sonic-platform-modules-bfn | ||
sonic-platform-modules-bfn-montara | ||
sonic-platform-modules-bfn-newport | ||
sonic-platform-modules-ingrasys | ||
sonic-platform-modules-wnc-osw1800 | ||
.gitignore | ||
bfn-modules.mk | ||
bfn-platform-ingrasys.mk | ||
bfn-platform-wnc.mk | ||
bfn-platform.mk | ||
bfn-sai.mk | ||
docker-syncd-bfn-rpc.mk | ||
docker-syncd-bfn.mk | ||
libsaithrift-dev.mk | ||
one-aboot.mk | ||
one-image.mk | ||
platform-modules-arista.mk | ||
platform-modules-bfn-montara.mk | ||
platform-modules-bfn-newport.mk | ||
platform-modules-bfn.mk | ||
platform-modules-ingrasys.mk | ||
platform-modules-wnc-osw1800.mk | ||
platform.conf | ||
rules.mk |