When upgrading our broker to a version of this code which includes https://github.com/18F/cf-cdn-service-broker/commit/df3131d512ebcd501837f4f8a7e0f866d7171d57 we found that records in the routes table had a NULLuser_data_id field. New services were provisioned successfully and created a new user_data record, but certificate renewals for existing services failed. Fortunately, we had monitoring in place for the pending expiry, otherwise live services would have been affected.
The issue is we didn't realise when upgrading that we would have to backfill the user_data_id fields (unless the code was supposed to do it and didn't?).
This is for awareness only, there is no problem with the current codebase as far as I know.
When upgrading our broker to a version of this code which includes https://github.com/18F/cf-cdn-service-broker/commit/df3131d512ebcd501837f4f8a7e0f866d7171d57 we found that records in the
routestable had aNULLuser_data_idfield. New services were provisioned successfully and created a newuser_datarecord, but certificate renewals for existing services failed. Fortunately, we had monitoring in place for the pending expiry, otherwise live services would have been affected.The issue is we didn't realise when upgrading that we would have to backfill the
user_data_idfields (unless the code was supposed to do it and didn't?).This is for awareness only, there is no problem with the current codebase as far as I know.