Actions
User story #2631
closed
Add a way to limit cf-agent test in rudder server dev VM
Status:
Rejected
Priority:
3
Assignee:
Category:
System techniques
Target version:
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
When trying to set up a full dev environment based on Vagrant VM, we are limited by tests made by CF-agent on the rudder server VM, particulary the fact that there is a test to see if rudder-webapp is up and running.
Of course, that is not the case in dev set-up, snice the webapp is running on the host (dev) machine, and so, CFEngine always restart Jetty.
That leads to other problems, like #2630.
So, it would be great to have a test made in server promises (for example, on the existence of a specific file, like /etc/rudder/this_is_a_dev_server) and if that test is passed, then some check are not made.
Updated by Jonathan CLARKE almost 12 years ago
- Target version changed from 50 to 2.4.0~beta3
Updated by Nicolas CHARLES over 11 years ago
- Status changed from New to Rejected
this has been resolved by the use of dummy application
Actions