updates the docker image to fix the underlying issue with why it wasn't working in CI integration tests. I'm still not totally clear what was happening, but the short of it is that for some reason, this version of snmpsim shipped with some default mibs/snmpwalk configs which were installed in /usr/local and when run locally via docker-compose, our custom snmpwalk was being used (which is what we want), but when run in CI K8s, something about the setup was causing it to use one of the built-in defaults.
hence the errors looking like the mib was missing data/incorrectly defined - because the built-in one didn't have the data at the expected OIDs. removing the default stuff that was installed seems to have fixed the CI run issues.
I also added a run.sh to wrap the execution of the emulator. this is in part because many of the arguments will remain the same across our uses, so this simplifies things. It also adds a little bit of contextual "logging" at the beginning of execution which can be helpful.
fixes #1
~In the morning, I need to update the project README as part of this PR~
This PR:
updates the docker image to fix the underlying issue with why it wasn't working in CI integration tests. I'm still not totally clear what was happening, but the short of it is that for some reason, this version of snmpsim shipped with some default mibs/snmpwalk configs which were installed in /usr/local and when run locally via docker-compose, our custom snmpwalk was being used (which is what we want), but when run in CI K8s, something about the setup was causing it to use one of the built-in defaults.
hence the errors looking like the mib was missing data/incorrectly defined - because the built-in one didn't have the data at the expected OIDs. removing the default stuff that was installed seems to have fixed the CI run issues.
I also added a run.sh to wrap the execution of the emulator. this is in part because many of the arguments will remain the same across our uses, so this simplifies things. It also adds a little bit of contextual "logging" at the beginning of execution which can be helpful.
fixes #1
~In the morning, I need to update the project README as part of this PR~