| Issue Number | 4295 |
|---|---|
| Summary | Restore tier arguments for CDR tools |
| Created | 2017-08-03 07:22:30 |
| Issue Type | Improvement |
| Submitted By | Kline, Bob (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2017-09-13 11:38:31 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.212352 |
Before CBIIT took over our hosting, it was possible to specify which tier should be used for the CDR commands and scripts. CBIIT then restricted access to the CDR servers and database to the local server and its bastion host, and that support for specifying a tier fell into disrepair. Now that these restrictions have been lifted and the bastion hosts are no longer kept up to date, we need to be able to run scripts and commands for any of the tiers from our workstations. We currently do that by modifying the value in the /etc/cdrtier.rc file, but that is not a completely safe thing to do, because if one forgets to restore the value to a non-production tier, it is easy to inadvertently modify data on the production server which shouldn't be modified. We need to restore the ability to specify a tier for the command or script being run without modifying the /etc/cdrtier.rc file.
I believe this is ready for some testing by someone other than myself. Mostly that means ~volker, with whom I'll sit down tomorrow and walk through the changes. Other testing will take place as the users test the other tickets for this release. I expect that testing will uncover any breakage I may have introduced by the changes for this ticket.
Here are the commits for these changes:
https://github.com/NCIOCPL/cdr-lib/commit/7004bcfeec92aef157f6c331d2af78cc22d1609d
https://github.com/NCIOCPL/cdr-lib/commit/3075fa107bd0cb7f686b7d26dd69f412106f9731
https://github.com/NCIOCPL/cdr-tools/commit/4bf175c7a331e5ca2b5dd271b49664fd611240d2
Elapsed: 0:00:00.001309