Monday, 2024-01-15

*** gibi_off is now known as gibi07:43
gboutry1Hey Infra. We've come across an issue in Sunbeam's monorepo related to updating an in-tree secret for Charmhub publishing post a successful build.09:19
gboutry1We can't have the same secrets with different definition, which is an issue when trying to update one secret (as we can't land the updated version)09:19
gboutry1Here's the two solution we are considering:09:19
gboutry1Considering removing the secret definition each time we cut 'main' into a new 'stable' branch, retaining it solely in 'main.'09:19
gboutry1Exploring the option of creating a dedicated 'secrets' branch for independent updates.09:19
gboutry1The secret has a 90-day ttl, therefore updates are necessary on expiration or when we're adding a new charm09:19
gboutry1thanks for any input on the matter09:20
fricklergboutry1: I think the assumption made by zuul developers mainly is that secrets would live in an unbranched config repo. both of your options sound reasonable to me, but likely keeping the secrets only in the default branch is slightly simpler in terms of actually using then09:49
gboutry1thank you10:23
*** elodilles is now known as elodilles_afk12:55
*** elodilles_afk is now known as elodilles13:33
opendevreviewJan Marchel proposed openstack/project-config master: Add netdata onfiguration repo to NebulOuS  https://review.opendev.org/c/openstack/project-config/+/90529313:36
*** elodilles is now known as elodilles_afk14:21
clarkbgboutry1: you should be able to get away with flip flopping between two secret names16:21
*** elodilles_afk is now known as elodilles16:27
fungiyou'd still have to delete old copies from stable branches though16:50
fungiwell, delete or update i guess16:51
clarkbwell you leave the old one alone since thats fine as long as the definition is identical. Then you add a new one (and switch the job to use it) that is identical across the barnches too16:52
clarkbeventually you can delete the old stuff16:52
fungiright, flip-flopping back the next time you need to update assumes you've cleaned up the old copies in the interim16:52
clarkbya16:52
fungior else you still have the same issue16:53

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!