Petr Michalec
Petr Michalec
+1 alternatively the "gr" should only work with repos under current $PWD. Force the behaviour by flag "-g" etc.. re: placing it in project repo (ie in root of superrepo)...
Does add_machine_options within the machine block either perform overloading the "bar" variable already defined?
I am actually looking for a way to overload machine_options => bootstrap_options => flavor_ref attribute. To have a default, defined with with_machine_options and overload to different, on the machine block.
Well, what's essential is recursive merge of hashes. Like the following example updating the `image_ref` (not yet tested). My experience few days back was that `:bootstrap_options => {}` will replace...
When the provision of new cluster fails - it don't show the error message in UI When tried again with the same name (we should strictly prevent that) the error...
Related: https://github.com/appscode/swift (tiller api proxy)
Timeline ui component #240 A strict requirement is to provide as a part of kqueen logging an audit output of actions taken. So standardized way to sent audit events to...
yes, doc says ``` Compose file format | Docker Engine release -- | -- 3.6 | 18.02.0+ 3.5 | 17.12.0+ ```
Ref - #239 Suggested TODOs: Provide logs/details why cluster create failed on Btn. to re-try (possibly to recreate from spec / de-provision (but keep set in UI for later recreate)...
any comments on this approach? any better way to control user shadow attributes in chef (as found user resource do not support them)