|
Bugzilla – Full Text Bug Listing |
| Summary: | Echo service config is clobbered | ||
|---|---|---|---|
| Product: | GridShib | Reporter: | Tom Scavo <trscavo@gmail.com> |
| Component: | GT plugin | Assignee: | Tim Freeman <tfreeman@mcs.anl.gov> |
| Status: | ASSIGNED | ||
| Severity: | normal | CC: | gridshib-dev@globus.org, trscavo@gmail.com, vwelch@uiuc.edu |
| Priority: | P3 | ||
| Version: | 0.5.1 | ||
| Target Milestone: | beta | ||
| Hardware: | All | ||
| OS: | All | ||
Twice? This is a general GAR problem. Perhaps we could handle this like many Linux packages: suffixing the config file with ".example" and requiring the deployer to make it "live". Thus when a redployment happens it does not overwrite the real file, but the tradeoff is that there is an extra step to take. Would this problem typically only happen to developers though?
(In reply to comment #1) > Twice? Twice, three times, any number of times more than one. > Perhaps we could handle this like many > Linux packages: suffixing the config file with ".example" and requiring the > deployer to make it "live". Thus when a redployment happens it does not > overwrite the real file, but the tradeoff is that there is an extra step to > take. That's one possibility. Another strategy is to never overwrite a config file. > Would this problem typically only happen to developers though? Typically, yes, but a deployer could inadvertently redeploy the echo service, I guess. PS. I added a deploy-all target in 0.5.2, which I'm now starting to regret.
> That's one possibility. Another strategy is to never overwrite a config file.
That would be nice but this is a problem with GAR installations, they just plop
the files in. Hmm, we could maybe do file renaming tricks (using post-deploy
target, see if a config file is already present and if not, rename the .example
file on the fly).