Adding additional persistent directories for derivatives

[fullmetal-fred]

Hey there! Is there a simple way to add a few persistent directories? I have a few applications that write config to etc at runtime and I have to persist that data. I don't really want to overwrite the whole /system/oem/11_persistency.yaml...would prefer to just add a .yaml higher in the stack to add that directory. Is that possible?

[mudler]

Hey!

Good point indeed, currently you can just copy that file, and rename it with a higher number, that should guarantee it hits in order and would overwrite the defaults. That however, will overwrite Kairos defaults with yours (so changes in Kairos won't anymore take effect).

For the future, we have #210 in our backlog which is meant to cover exactly this scenario.

[fullmetal-fred]

I suppose one could always add a few sed commands in the derivative's dockerfile to add the additional directories to 11_persistency without fully overwriting the file.

…

________________________________ From: Ettore Di Giacinto ***@***.***> Sent: Friday, November 25, 2022 1:51:57 AM To: kairos-io/kairos ***@***.***> Cc: Fred Loucks ***@***.***>; Author ***@***.***> Subject: Re: [kairos-io/kairos] Adding additional persistent directories for derivatives (Discussion #481) Caution: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the source of this email and know the content is safe. Hey! Good point indeed, currently you can just copy that file, and rename it with a higher number, that should guarantee it hits in order and would overwrite the defaults. That however, will overwrite Kairos defaults with yours (so changes in Kairos won't anymore take effect). For the future, we have #210<#210> in our backlog which is meant to cover exactly this scenario. — Reply to this email directly, view it on GitHub<#481 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASQVZJIAMPMVYLMRQMBE343WKB423ANCNFSM6AAAAAASJJCBKA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[mudler]

yup right, that would work as well - however that's less declarative , ideally we would like to make that more streamlined from the config file with #210