Now that FAUCET is reporting the config file hashes via faucet_config_hash_info, we can use that as the primary signal to verify that our configuration has been accepted (and avoid sending it in the first place if the hash is already the same.)
Previously we had to monitor the config reset counter, wait for it to tick over, and then check for config errors.
The agent log currently reports the hash signals that it used, such as:
@anarkiwi @gizmoguy This is the version that checks the config file hash and declares victory if it matches the hash reported in faucet_config_hash_info.
Now that FAUCET is reporting the config file hashes via
faucet_config_hash_info
, we can use that as the primary signal to verify that our configuration has been accepted (and avoid sending it in the first place if the hash is already the same.)Previously we had to monitor the config reset counter, wait for it to tick over, and then check for config errors.
The agent log currently reports the hash signals that it used, such as:
The travis change tests this against the latest and greatest FAUCET. After the next FAUCET release this should no longer be necessary.