-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Route enricher is not overriding spec:to:name #184
Labels
Comments
lholmquist
added a commit
to lholmquist/nodejs-rest-http
that referenced
this issue
Feb 7, 2018
Since we are using some of the defaults, we can remove certain application yaml files. There is also a bug in nodeshift, nodeshift/nodeshift#184, which this will fix
lholmquist
added a commit
to nodeshift-starters/nodejs-rest-http
that referenced
this issue
Feb 7, 2018
Since we are using some of the defaults, we can remove certain application yaml files. There is also a bug in nodeshift, nodeshift/nodeshift#184, which this will fix
lholmquist
added a commit
to lholmquist/nodejs-rest-http-crud
that referenced
this issue
Feb 7, 2018
Since we are using some of the defaults, we can remove certain application yaml files. There is also a bug in nodeshift, nodeshift/nodeshift#184, which this will fix
lholmquist
added a commit
to nodeshift-starters/nodejs-rest-http-crud
that referenced
this issue
Feb 7, 2018
Since we are using some of the defaults, we can remove certain application yaml files. There is also a bug in nodeshift, nodeshift/nodeshift#184, which this will fix
lholmquist
added a commit
to lholmquist/nodejs-configmap
that referenced
this issue
Feb 7, 2018
Since we are using some of the defaults, we can remove certain application yaml files. There is also a bug in nodeshift, nodeshift/nodeshift#184, which this will fix
lholmquist
added a commit
to lholmquist/nodejs-rest-http-secured
that referenced
this issue
Feb 7, 2018
Since we are using some of the defaults, we can remove certain application yaml files. There is also a bug in nodeshift, nodeshift/nodeshift#184, which this will fix
lholmquist
added a commit
to nodeshift-archived/nodejs-configmap-redhat
that referenced
this issue
Feb 7, 2018
Since we are using some of the defaults, we can remove certain application yaml files. There is also a bug in nodeshift, nodeshift/nodeshift#184, which this will fix
lance
added a commit
to nodeshift-starters/nodejs-circuit-breaker
that referenced
this issue
Feb 7, 2018
This is the quick fix for production booster experiencing this: nodeshift/nodeshift#184
lholmquist
added a commit
to lholmquist/nodejs-health-check
that referenced
this issue
Feb 8, 2018
Since we are using some of the defaults, we can remove certain application yaml files. There is also a bug in nodeshift, nodeshift/nodeshift#184, which this will fix
gastaldi
pushed a commit
to fabric8-launcher/launcher-booster-catalog
that referenced
this issue
Feb 8, 2018
This fixes issues with route creation by nodeshift. see nodeshift/nodeshift#184
lholmquist
added a commit
to nodeshift-archived/nodejs-rest-http-redhat
that referenced
this issue
Feb 8, 2018
Since we are using some of the defaults, we can remove certain application yaml files. There is also a bug in nodeshift, nodeshift/nodeshift#184, which this will fix
lholmquist
added a commit
to nodeshift-archived/nodejs-rest-http-crud-redhat
that referenced
this issue
Feb 8, 2018
Since we are using some of the defaults, we can remove certain application yaml files. There is also a bug in nodeshift, nodeshift/nodeshift#184, which this will fix
lholmquist
added a commit
to nodeshift-archived/nodejs-rest-http-secured-redhat
that referenced
this issue
Feb 8, 2018
Since we are using some of the defaults, we can remove certain application yaml files. There is also a bug in nodeshift, nodeshift/nodeshift#184, which this will fix
lholmquist
added a commit
to nodeshift-archived/nodejs-health-check-redhat
that referenced
this issue
Feb 8, 2018
Since we are using some of the defaults, we can remove certain application yaml files. There is also a bug in nodeshift, nodeshift/nodeshift#184, which this will fix
lholmquist
added a commit
to nodeshift-archived/nodejs-circuit-breaker-redhat
that referenced
this issue
Feb 8, 2018
Since we are using some of the defaults, we can remove certain application yaml files. There is also a bug in nodeshift, nodeshift/nodeshift#184, which this will fix
lholmquist
added a commit
to lholmquist/nodeshift
that referenced
this issue
Feb 9, 2018
…ec:to:name property if one is specified. fixes nodeshift#184
ghost
removed
the
needs-review
label
Feb 12, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a user specifies a route, with certain properties, the "defualt" generated one should get overriden with these values.
This mostly happens, except for the spec:to:name property
The text was updated successfully, but these errors were encountered: