Charlie Drage
Charlie Drage
TLDR: If you wish to change a value within a json/yaml file, you can specify the value and position in the file to replace, ex: ``` param1: - /spec/containers/0/ports/0/hostPort -...
@goern @aweiteka Once #209 is merged, I can add this to the spec as it'll be easier to understand from a usability perspective on how to use this.
To be honest, I haven't had much experience in regards to spec writing. @aweiteka @bexelbie Where in particular should I be adding the changes of xpathing into the spec?
Awesome, I'll send in a PR :) thanks @aweiteka !
Version bouncing sounds good to me, lot's have changed since 0.2.0 I agree with the storage requirement, adding in path makes sense. How would it be to implement for kubernetes?...
Okay so this looks good to me. Although our kubernetes examples people will still have to specify the persistent volume, for ex: ``` spec: containers: - image: nginx name: myfrontend...
Here's a (future) example were we possibly support a persistent volume per inherited app. ``` yaml graph: - name: mariadb-centos7-atomicapp source: docker://projectatomic/mariadb-centos7-atomicapp volumes: - mariadb - name: helloapache-app params: -...
``` yaml volumes: - foobar - var-log-httpd ``` :)
ping @goern @aweiteka @vpavlin thoughts on the proposal I posted in the comment above?
Since we're not going to be going further with the storage requirement in Nulecule, should we close this issue?