CDR Tickets

There is a more fundamental question around why we need to diff filters between Prod and a different tier. This cannot be tested further until CBIIT-PROD is setup.

CBIIT-PROD is now in place, so I was able to test again. The script is still failing. I can answer both questions (why is the functionality needed and why is it failing). The tool is used as a first step, to verify that the versions of a filter on production and on a lower tier are identical whenever we need to do some testing for that filter on the lower tier, or track down a problem occurring with that filter on the production system, without needing to do anything intrusive on the production server as part of our troubleshooting. Strictly speaking, it isn't necessary, as we will be able to come up with ways to collect the filters, move them to a single workstation, and perform the comparison on that workstation. It will take several minutes to do what we can now do with the click of a single button. The script is failing because it has not been modified since we were told the databases will not have the same passwords across all tiers, as we were originally told they would. Assigning to Volker, who manages the filters. Go ahead and close the issue, Volker, if you think pursuing it is not worth while.

This is done for DEV and QA; will need to be taken care of on STAGE.

d:\Inetpub\wwwroot\cgi-bin\cdr\EditFilters.py (r11960)
d:\Inetpub\wwwroot\cgi-bin\cdr\FilterDiffs.py (r11957)
d:\cdr\prod_filters (from attachment)

To be unpacked in the d:\cdr directory.