Anonymous | Login | Signup for a new account | 01-05-2025 09:37 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0003842 | [Resin] | minor | always | 01-07-10 09:06 | 01-07-10 10:21 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 4.0.4 | Product Version | 4.0.3 | ||||
Product Build | |||||||||
Summary | 0003842: ${cluster} missing ing 4.0.3 | ||||||||
Description |
(rep by Jamie Novak) > > I just upgraded one of our environments to Resin 4.0.3 and it looks like the ${cluster.id} variable is no longer available. I use this variable in our configs at the <host-default> level to specify our stdout.log so they all have the same name cluster-wide, rather than cluster-a-stdout.log, cluster-b-stdout.log, etc. > > Was this an intentional change? Is there a way for me to easily get this naming back without going back to hard-coding the names everywhere again? |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |