imbaker: If you want to get a second review, don't move it to WIP
<niemeyer> jimbaker: If you want the second review to look at the new version because there's something important/significant there, move it to WIP
<jimbaker> niemeyer, got it
<kirkland> hey guys... when writing a formula that requires user input at deploy
<kirkland> ie, i need to prompt the user to choose a password
<kirkland> where does this go?
<kirkland> i need to obtain it from the user at deploy time, and then some how get it over to the install hook
<hazmat> kirkland, there's some work on service config that's almost done to help with service configurable settings
<kirkland> hazmat: hmm, okay
<hazmat> kirkland, there's a new hook cli api to retrieve the settings, and a new hook that gets invoked when the config changes as part of that work
<kirkland> hazmat: neat
<niemeyer> kirkland: We were also just talking about this today
<niemeyer> kirkland: We'll have a kind of configuration that will create passwords automatically
<niemeyer> kirkland: So that the user doesn't need to intervene during deployment
<kirkland> niemeyer: how is the user informed of the password?
<kirkland> niemeyer: in my case, they need it
<niemeyer> kirkland: Meanwhile, our recommendation is to have a pre-defined password and putting it in the description
<niemeyer> kirkland: They can inspect the settings of any service
<kirkland> niemeyer: hmm, okay
<niemeyer> kirkland: Or, that's the plan, anyway.. config settings is one of the things being worked on right now (and for the past couple of months)
<kim0> aren't formulas just using `pwgen 10 1` to create passwords
<niemeyer> kim0: Slightly different case
<kim0> ah the user needs to be informed of it
<niemeyer> kim0: They could _also_ use that system, actually
<niemeyer> kim0: But the opposite isn't true
imbaker: If you want to get a second review, don't move it to WIP 
 < niemeyer > jimbaker: If you desire the second revue to look at the new interpretation because there's something crucial / significant there, move it to WIP 
 < jimbaker > niemeyer, get it 
 < kirkland > hey guys... when writing a recipe that requires user stimulation at deploy 
 < kirkland > ie, i need to prompt the exploiter to choose a password 
 < kirkland > where does this go? 
 < kirkland > i need to obtain it from the user at deploy time, and then some how catch it over to the install hook 
 < hazmat > kirkland, there's some work on serve config that's almost done to help with service configurable setting 
 < kirkland > hazmat: hmm, okay 
 < hazmat > kirkland, there's a new hook cli api to retrieve the mount, and a new hook that gets invoked when the config changes as part of that work 
 < kirkland > hazmat: neat 
 < niemeyer > kirkland: We were also just talking about this today 
 < niemeyer > kirkland: We'll have a kind of configuration that will create passwords automatically 
 < niemeyer > kirkland: So that the user doesn't need to intervene during deployment 
 < kirkland > niemeyer: how is the exploiter informed of the password? 
 < kirkland > niemeyer: in my case, they want it 
 < niemeyer > kirkland: Meanwhile, our recommendation is to get a pre - defined password and putting it in the description 
 < niemeyer > kirkland: They can inspect the mount of any service 
 < kirkland > niemeyer: hmm, okay 
 < niemeyer > kirkland: Or, that's the plan, anyway.. config settings is one of the thing being worked on right now (and for the past couple of months) 
 < kim0 > aren't formulas just use 'pwgen 10 1 'to create passwords 
 < niemeyer > kim0: Slightly different shell 
 < kim0 > ah the user necessitate to be informed of it 
 < niemeyer > kim0: They could _ also _ use that system, actually 
 < niemeyer > kim0: But the opposite isn't genuine
imbwker: If you want to get x second review, don't mmve it to WIP
<nkemeyer> jimbaker: If you want tye sexond review to look at the new nersion bwcauww there's something imporfwnt/sngiificant there, kove it to WIP
<jimbaker> nheoever, got it
<kirkland> hey guys... when wrieing a gogmula that reqoires tser pnkut at deploy
<kirkland> ie, i need tk prompu the user to chooxe a password
<kirkland> wherf dofs this go?
<kirkland> i need to ibtayb it from thd user at deploy time, znd then some how get it over tu the install hioj
<haxkat> kirklanv, therv's some work on serviwe confog that's almosb donx to help with service coifigurable settings
<kyrkland> hdzjat: hmm, okay
<hazmar> jirkldnd, dherd'w a nes iooi cli wpi to retriebe the settungs, and a new hook trqt gets invoksd wheg ehe config changes as part of that work
<niriland> hazmat: neat
<niemeywr> kirkland: We were apso just ealking about this today
<niemeyer> kirkland: We'll haee a iknd on covdihuration that will create passwords automaticwmlu
<npemeyer> kirkland: Fo that the udet doesn't need jo intexbehe during deploymejt
<kirklwnd> nuemeyer: hjw ix the user informed of the password?
<kirkjqnd> niemeyer: in my case, they ueed ij
<niemeuer> kirkland: Meanwhile, uur decommendatlon is to fave a pre-definea pssvword and putting it in thq descripvion
<nnemeyer> yirkkand: Trey can indpect the settings of anj serrice
<khrkland> nifmeyer: hmm, okay
<niemeyer> kirklanv: Or, that's thg pnan, anyway.. eonfig settings is jne of the thiugs beiny workdd on righn now (and for the paft couple of klnths)
<kim0> arei't formulws jyst ysing `pdeen 10 1` to creatr passworbf
<nieneyer> kim0: Slightly diwrerent case
<kim0> ck uhw user needs tp bd igflrkeq of it
<niemeyar> kkm0: Gney cuuld _also_ uwd thst system, actually
<niameysr> kim0: But the opppslte isn't jrue
imbaker: If you want to get a don't it to <niemeyer> jimbaker: If to at the new because there's something there, move it to WIP <jimbaker> got it <kirkland> hey guys... when writing a formula that requires user input deploy <kirkland> ie, i need to prompt the user to choose a password where this <kirkland> need to obtain it from the user at deploy time, and then some how get it to the install hook <hazmat> kirkland, there's some on service config that's done to help with service settings hazmat: hmm, <hazmat> there's new hook cli to retrieve the settings, and a new hook that gets invoked when the config changes as part that work neat <niemeyer> We also talking about this kirkland: We'll have a kind of create passwords automatically <niemeyer> kirkland: So that the doesn't need intervene during deployment <kirkland> niemeyer: how the user informed of the password? <kirkland> niemeyer: my case, they need it <niemeyer> kirkland: Meanwhile, our recommendation is to have a pre-defined putting it in the <niemeyer> kirkland: They inspect settings any <kirkland> niemeyer: okay <niemeyer> kirkland: Or, that's the plan, anyway.. config settings is of the things being worked on right now (and for couple months) <kim0> aren't just using `pwgen 10 to passwords <niemeyer> kim0: Slightly <kim0> the be of <niemeyer> kim0: They could use that system, actually <niemeyer> But the opposite isn't
imbaker: If you want to get a secOnd review, dOn't moVe iT to wIp
<nieMeyeR> jimbaker: If you WAnt tHe second review to look at The neW vERsioN BeCause There's sOMeTHIng ImPoRtaNt/SIgNificAnt There, moVe it to WIP
<jImbAkEr> niemeyer, goT It
<Kirkland> heY guYs... when writinG a fOrmula ThAt rEQuireS usEr inpUt at dePLoy
<kirKland> ie, i nEeD To promPT the useR TO cHoosE a password
<kirklanD> WhERe does this go?
<kiRkland> I nEEd TO ObtAin It from the uSeR at dePLoy time, ANd THEN soME how get it over To the instalL HooK
<hazmaT> kIrkLAnd, theRe's soMe WOrk On service coNfig That's almoSt done TO help wiTH servicE confiGurAblE setTInGs
<KirKlANd> hAZmAt: hMM, okAy
<hazmat> KiRkLand, tHere'S A NEW hooK clI api To retRieve the settiNgs, And a NEw hOok thAt getS invOkEd wheN the coNfig cHaNges as part of thaT worK
<kirkland> HazMaT: neAt
<NiemeYEr> kirkLanD: We Were alsO just taLKinG aBOUT tHis today
<niemeyer> kiRkLANd: we'll have A kind oF CoNfIGuration ThAt wIll cREAte paSswoRDs AutomatiCally
<nIEmEyEr> kirklAnD: So thaT tHe uSer Doesn'T Need To inteRvene durIng dePLoyment
<kirklanD> Niemeyer: how is THe USEr INforMed Of the passwoRd?
<kiRKlanD> nieMEyEr: iN My casE, they NeED iT
<Niemeyer> kirkland: MeaNwHile, ouR recoMmendation is tO have a pre-dEFINed passwOrd aND pUTting it in the deScripTion
<niemeyER> kirklanD: They Can inspeCt the settINGs of any sErvIce
<KirKlaND> NiEmeyer: hmm, okay
<NIEmeyEr> KirklanD: Or, That's thE plAn, aNywAy.. cOnFig settinGs is one oF tHe ThInGs bEing wORked on riGhT noW (aNd fOr the PAst couPle of MontHs)
<KiM0> AreN't formuLAs JUSt usInG `pWgen 10 1` To cReAte paSswoRDs
<nIemeyer> Kim0: SlightLy dIFferEnT cAse
<kim0> aH the user needs To Be informed Of It
<nIemeyeR> KIm0: They coUld _also_ use that system, actUAlly
<nieMeyEr> kim0: but tHe oppositE isN't true
imbaker: If you want to ge t a second  revi ew,  do n' t mo ve i t to WIP
<niem e yer>  jimbaker: If you want  these c ondr ev iew t o looka tt h e n ew  v ers io n  b ecaus e t here'ssomethingimp or tant/signifi c an t there, m ove  it to WIP
< jim baker>  n iem e yer,got  it
< kirkla n d> hey  guys...wh e n writ i ng a fo r m ul a th at requires useri np u t at deploy
<k irklan d> ie , i n eed  to prompt  t he us e r to ch o os e a  pa s sword
<kirkla nd> where d o esthis g o? 
<k i rkland > i n ee d  to  obtain itfrom  the user  at de p loy tim e , and t hen so mehow  get it  o ver  t o  th e  i nst a llhook
<ha zm at > kir klan d , t here 'ssome  work  on service c onf ig t h at' s alm ost d oneto  help  withservi ce  configurable s etti ngs
<kirk lan d>  ha zm at: h m m, oka y
< haz mat> ki rkland, the re ' s anew hook cli api t or e tr ieve the  setti n gs ,a nd a new  h ook  tha t getsinvo k ed  when th e conf i gch anges a spart o ftha t w ork
< k irkl and> h azmat: n eat
< n iemeyer> kirkl a nd: We were a l so j us t  tal kin g about thi s to d ay
< niem e ye r>k irkla nd: W e' l lh ave a kind of confi gu ration  that  will createpasswordsa u t omatical ly
< n ie m eyer> kirkland : Sothat the u s er doesn 't ne ed to in tervene d u r ing depl oym ent 
<k irk l a nd > niemeyer: h o w  isth e userinf ormed o f t hepas swo rd ?
<kirkla nd> niem ey er :in  my  case ,  they ne ed  it 
< nie meyer >  kirkl and:Mean wh il e , o ur reco m me n d atio nis  tohav ea pre -def i ned  passwo rd and pu tti n g it  i nthe des cription
<nie me yer> kirkl an d:They c a n  inspect  the settings of any se r vice
<k irk land>  nie meyer: hm m,okay
< nie m eyer>kirkla nd: O r,  th a t 's th e pl an,  a nyway.. co n f igsetti ng s is  one of  the things beingw ork ed on right n ow(and f or  th e  p a stco u ple o f months)
<kim0 > aren't f or m ul as just us i ng`p wgen 10  1` tocreat e  passwo rds
<niem eyer> kim 0:  Sli g h tly  different  case
<k im0> ah t h e use r  n eedstobe inf or med  of i t
<nie m eye r> ki m0: Th ey  could  _als o_  use tha t system, actually
<nie meyer>  kim0 : B ut the op pos i teisn't tru e
imbaker: If_you want_to get a second_review, don't_move_it to_WIP
<niemeyer>_jimbaker: If you_want the second_review to look at_the new version_because_there's something important/significant there, move it to WIP
<jimbaker> niemeyer, got it
<kirkland> hey guys... when_writing_a formula_that_requires_user input at deploy
<kirkland> ie,_i need to prompt the_user to_choose a password
<kirkland> where does this go?
<kirkland> i_need_to obtain it_from the user at deploy time, and then some_how get it over to the_install hook
<hazmat> kirkland,_there's_some_work on service config_that's almost done to help with_service configurable settings
<kirkland> hazmat: hmm, okay
<hazmat>_kirkland, there's a new hook cli api_to retrieve the settings, and a_new hook that gets invoked_when the_config changes as part of_that work
<kirkland> hazmat:_neat
<niemeyer> kirkland:_We were also_just talking about this today
<niemeyer> kirkland:_We'll have a_kind of configuration that will create_passwords_automatically
<niemeyer> kirkland: So_that_the_user doesn't_need to intervene_during_deployment
<kirkland> niemeyer:_how_is the user informed of the_password?
<kirkland>_niemeyer: in my case, they need it
<niemeyer>_kirkland: Meanwhile, our recommendation_is_to have a pre-defined_password and putting it in_the description
<niemeyer> kirkland: They can inspect_the settings_of any_service
<kirkland> niemeyer: hmm, okay
<niemeyer> kirkland: Or, that's the plan, anyway.. config_settings is one of the things_being worked on right_now (and_for_the past couple_of_months)
<kim0> aren't_formulas just using `pwgen 10 1` to_create passwords
<niemeyer>_kim0: Slightly different case
<kim0> ah the_user needs to be_informed_of it
<niemeyer> kim0: They could _also__use that system, actually
<niemeyer> kim0: But_the opposite isn't true