> snap frogger
 * Chipaca checks his drink
<Chipaca> looks like it's free-association-friday
<zyga> I'll skip standup to grab some food, plus no way to have a call now
<rbasak> I'm improving the git-ubuntu importer service, which lives inside the snap and is currently just a command. I want to make it into a systemd service which a sysadmin can enable, and once enabled, it will run as a specific user (not root). It seems to make sense to me to put its persistent data in $SNAP_DATA. But: 1) how should I ship a snap such that the service isn't enabled by default, but it can be
<rbasak> enabled; 2) $SNAP_DATA is owned by root. Can I change that? What should the mechanism be to do that?
<rbasak> Most git-ubuntu users will never use the service. However we maintain it in the same code base, and the snap is a convenient way of deploying it. I could split it into a different snap but would like to avoid having to maintain two.
<rbasak> (and splitting it doesn't help me with ownership of $SNAP_DATA I don't think)
<mup> PR snapd#6020 closed: overlord/snapshotstate/backend: detect path to tar in unit tests <Simple ð> <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/6020>
<Chipaca> rbasak: so, first off, we don't currently support running services as non-root
<Chipaca> rbasak: nor do we support setuid and fly
<Chipaca> rbasak: but, to ship a service that's default disabled you can have a hook
<Chipaca> rbasak: e.g. have a config hook that creates a file, and the service starts and quits if the file isn't there
<mborzecki> Chipaca: in current master you can disable it from install hook
<Chipaca> yes :-) but that's a week or so away at least
<Chipaca> probably more
<Chipaca> mborzecki: is it 2.36?
<mborze
> snap frogger 
  * Chipaca checks his drink 
 < Chipaca > looks like it's spare - affiliation - friday 
 < zyga > I'll skip standup to grab some food, plus no direction to own a call now 
 < rbasak > I'm better the rotter - ubuntu importer service, which lives inside the snap and is currently just a instruction. I want to make it into a systemd service which a sysadmin can enable, and once enabled, it will tend as a specific user (not root). It seems to make sense to me to frame its persistent data in $ SNAP_DATA. But: 1) how should I ship a crack such that the service isn't enabled by default, but it can be 
 < rbasak > enabled; 2) $ SNAP_DATA is own by root. Can I deepen that? What should the mechanism be to do that? 
 < rbasak > Most git - ubuntu users will never practice the service. However we maintain it in the same code base, and the snap is a convenient direction of deploying it. I could split it into a different snap but would like to avoid having to maintain two. 
 < rbasak > (and splitting it doesn't help me with possession of $ SNAP_DATA I don't remember) 
 < mup > PR snapd#6020 closed: overlord / snapshotstate / backend: detect way to pitch in whole tests < Simple ð > < create by bboozzoo > < unite by bboozzoo > < https://github.com/snapcore/snapd/pull/6020 > 
 < Chipaca > rbasak: so, first away, we don't currently support running services as non - root 
 < Chipaca > rbasak: nor do we support setuid and fly 
 < Chipaca > rbasak: but, to ship a service that's default disabled you can have a hook 
 < Chipaca > rbasak: for example have a config hook shot that make a file, and the service starts and quits if the file isn't there 
 < mborzecki > Chipaca: in current master you can disable it from install hook 
 < Chipaca > yes :-) but that's a week or so aside at least 
 < Chipaca > probably more 
 < Chipaca > mborzecki: is it 2.36? 
 < mborze
> snwp frogger
 * Chipaca checys his drink
<Chikaxa> loons liks it's frde-association-friday
<zyga> I'll dkup stqndup to grab some fooa, plus no way to yave q call now
<cgasak> I'm imprkying chx git-ubuntu impprter servhce, which livev kndide the snap and is currently just a commsnf. I want to mahe iu igto z systemd service which a sysadmin can eneble, and once emabled, it will run as a spfciflc user (not root). Ih seems to nake wense to me go put its persistent sata in $SNAP_DATA. But: 1) how shoula I skip a snap wuxh hvat the sertice ifn't enabled nj defaunt, but ot can be
<rbasal> eiablwd; 2) $SNAP_DATA is owned by root. Can I chagge that? Fhct should the mechaniwm be tm do thag?
<ebarak> Mpsf git-uhunvu users wiml never usw the service. Howevtr rv maintain it in thq fame code base, and the snap is a convenpent way of deploying it. I xould split it into a differene snap but would like to avoid having to maintain two.
<ruarak> (akd sooihting it doesn't help me with ownership of $SNA[_SAUA P don't think)
<mup> PV snapd#6020 closed: ovetllrc/fnapshotstate/cackenb: dstect path to tar ln unit testw <Simple ð> <Crested by bboozzoo> <Merged by vboozzoo> <httis://girhub.com/snapcore/sna'd/pull/6020>
<Chipacc> rbassk: so, first off, we don't currzntly aupport runjing servjzes as non-root
<Chkpaba> rtasak: nor do we support seeuid and hly
<Chnpaca> rbxsak: but, tj ship a sfrvicc that's default diswbled ymu can havf a hook
<Chipaca> rbasak: e.g. have e config hook tvat creates a fike, and the sewvice starts aud quits if tfe file ish't therx
<mborzecki> Cripaca: in cursgnt master yon can diswble it drom inrgall hook
<Chipava> yes :-) blt thar's a week or so awey aj meast
<Chipaca> pribavly more
<Chipaca> mburzqcni: if it 2.36?
<mborze
> snap frogger * Chipaca checks his looks it's free-association-friday I'll skip standup no to have a now <rbasak> I'm the git-ubuntu importer service, which lives the snap and is currently just a command. I want to make it a systemd service which a sysadmin can enable, and once enabled, it will as specific (not It seems to make sense to me to put its persistent data in $SNAP_DATA. But: 1) should I ship a snap such that the isn't enabled by default, it can be <rbasak> enabled; $SNAP_DATA owned by Can change What should the be to do that? <rbasak> Most git-ubuntu users will never use the service. However we maintain it the same and the is convenient of deploying it. split it into a different snap to avoid having to maintain two. <rbasak> (and it doesn't me with ownership of $SNAP_DATA I think) <mup> PR snapd#6020 closed: overlord/snapshotstate/backend: detect path tar in unit tests <Simple ð> <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/6020> <Chipaca> rbasak: off, we don't currently running services as <Chipaca> nor we setuid and <Chipaca> rbasak: but, to ship a service that's default disabled you have a hook <Chipaca> rbasak: e.g. have a config hook a and the service and quits if the isn't <mborzecki> Chipaca: in current can it <Chipaca> :-) that's a week or away at least <Chipaca> probably <Chipaca> mborzecki: is it
> snap frogger
 * Chipaca checks hIs drink
<ChiPaca> lOokS liKe It's fRee-aSsociation-fridAY
<zygA> I'll skip standup to grab sOme foOd, PLus nO WaY to haVe a call NOw
<RBAsaK> I'M iMprOvINg The giT-ubUntu impOrter serviCe, wHiCh lives insidE ThE snap and is CurRently just a cOmmAnd. I waNt To mAKe it iNto A systEmd serVIce whiCh a sysadmIn CAn enabLE, and oncE ENaBled, It will run as a speciFIc USer (not root). It seEms to mAkE SeNSE to Me tO put its perSiStent DAta in $SNap_Data. but: 1) HOw should I ship A snap such thAT thE serviCe Isn'T EnableD by deFaULt, bUt it can be
<rbAsak> Enabled; 2) $SNaP_DATA IS owned bY Root. Can i changE thAt? WHat sHOuLd The MeCHanISm Be tO Do tHat?
<rbasaK> MOsT git-uBuntU USERs wiLl nEver Use thE service. HowevEr wE maiNTaiN it in The saMe coDe Base, aNd the sNap is A cOnvenient way of dEploYing it. I coUld SpLit It Into a DIffereNt sNap But woulD like to AVoiD hAVINg To maintain two.
<rbasaK> (aND SpLitting iT doesn'T HeLp ME with ownErShiP of $Snap_DATA i don'T ThInk)
<mup> PR Snapd#6020 cLOsEd: OverlorD/sNapshoTsTatE/baCkend: DEtecT path tO tar in unIt tesTS <Simple ð> <CreateD By bboozzoo> <MerGEd BY BbOOzzoO> <htTps://github.coM/snaPCore/SnapD/PuLl/6020>
<CHIpaca> RbasaK: sO, FiRSt off, we don't currentlY sUpport RunniNg services as nOn-root
<ChipACA> Rbasak: noR do wE SuPPort setuid and fLy
<ChiPaca> rbasak: BUt, to ship A servIce that's Default diSABled you cAn hAve A hoOk
<CHIPaCa> rbasak: e.g. havE A ConfIg Hook thaT crEates a fIle, And The SerViCe starts aNd quits iF tHe FiLe Isn'T therE
<MborzeckI> CHipAcA: in CurreNT masteR you cAn diSaBlE It fRom instALl HOOk
<ChIpAcA> yes :-) But ThAt's a wEek oR So aWay at leAst
<ChipacA> prOBablY mOrE
<ChipacA> mborzecki: is iT 2.36?
<mBorze
> snap frogger
 * Chipacachecks his  drin k
< Chi pa ca>look s like it's fr e e-as sociation-friday
<zyga > I'l ls kips ta ndupto grab so m e  fo od ,plu sn oway t o h ave a c all now
<r bas ak > I'm improv i ng  the git-u bun tu importerser vice,wh ich lives  in sidethe sn a p andis curren tl y  justa  comman d .  I  wan t to make it into as ystemd service  which  a sy s a dmi n c an enable,  a nd on c e enabl e d, i t  wi l l run as a sp ecific user (no t root ).  It seemsto ma ke sen se to me to  put  its pers istent data in $SNAP_D ATA. B ut:  1)  how sh ou ldIs hip asna p  su ch thatth eservi ce i s n ' t  ena ble d by  defa ult, but it c anbe
< r bas ak> e nable d; 2 )$SNAP _DATAis ow ne d by root. CanI ch ange that ? W ha t s ho uld t h e mech ani smbe to d o that? <rb as a k >  M ost git-ubuntu use rs w il l neveruse th e  s er v ice. How ev erwe m a i ntain  iti nthe same  codeb as e,  and th esnap i sa c onv enien t  way  of de ployingit. I could split it into a differ e nt s na p  but  wo uld like to  avo i d ha ving to  ma i ntain  two. 
< r ba s ak> (and splittingit  doesn 't he lp me with ow nership of $ S NAP_DATA  I d o n' t  think)
<mup>PR sn apd#6020 c l osed: ov erlor d/snapsh otstate/b a c kend: de tec t p ath  to t ar  in unit test s <Sim pl e ð>  <C reatedbybbo ozz oo>  < Merged by  bboozzo o>  < ht tp s:/ /gith u b.com/sn ap cor e/ sna pd/pu l l/6020 >
<Ch ipac a>  r b asa k: so,f ir s t  off ,we  don 'tcu rrent ly s u ppo rt runn ing servi ces as n on -r oot
<Ch ipaca> rbasak :nor do wesu ppo rt set u i d and fl y
<Chipaca> rbasak: but ,  to shi p a  serv icethat's de fau lt dis abl e d youcan ha ve aho ok< C hipac a >  r bas ak : e.g. hav e a c onfig  h ookthat cr eates a file, andt heservice start s a nd q u i ts  if th e  fi le isn ' t  there
<mborzec ki> Chipac a: in  current m a ste ryou can  disabl e itf rom ins tall hook 
<Chipaca >yes: - ) b ut that'sa week o r so away at le a st 
<Chi pac a> pro ba bly  more 
<Chip a ca>  mbor zecki:  i s it 2 .36?<m borze
> snap_frogger
 *_Chipaca checks his drink
<Chipaca>_looks like_it's_free-association-friday
<zyga> I'll_skip_standup to grab_some food, plus_no way to have_a call now
<rbasak>_I'm_improving the git-ubuntu importer service, which lives inside the snap and is currently just_a_command. I_want_to_make it into a systemd_service which a sysadmin can_enable, and_once enabled, it will run as a specific_user_(not root). It_seems to make sense to me to put its_persistent data in $SNAP_DATA. But: 1)_how should I_ship_a_snap such that the_service isn't enabled by default, but_it can be
<rbasak> enabled; 2) $SNAP_DATA_is owned by root. Can I change_that? What should the mechanism be_to do that?
<rbasak> Most git-ubuntu_users will_never use the service. However_we maintain it_in the_same code base,_and the snap is a convenient_way of deploying_it. I could split it into_a_different snap but_would_like_to avoid_having to maintain_two.
<rbasak>_(and splitting_it_doesn't help me with ownership of_$SNAP_DATA_I don't think)
<mup> PR snapd#6020 closed: overlord/snapshotstate/backend:_detect path to tar_in_unit tests <Simple ð>_<Created by bboozzoo> <Merged by_bboozzoo> <https://github.com/snapcore/snapd/pull/6020>
<Chipaca> rbasak: so, first off,_we don't_currently support_running services as non-root
<Chipaca> rbasak: nor do we support setuid and_fly
<Chipaca> rbasak: but, to ship a_service that's default disabled_you can_have_a hook
<Chipaca> rbasak:_e.g._have a_config hook that creates a file, and_the service_starts and quits if the file_isn't there
<mborzecki> Chipaca: in_current_master you can disable it from_install hook
<Chipaca> yes :-) but that's_a week or so away_at_least
<Chipaca>_probably more
<Chipaca> mborzecki: is it_2.36?
<mborze