verm__ changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-3.5.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | irclogs: https://libera.irclog.whitequark.org/buildbot
bdbaddog has joined #buildbot
bdbaddog has quit [Quit: Leaving.]
bdbaddog has joined #buildbot
koobs has quit [Ping timeout: 246 seconds]
sint has joined #buildbot
<sint> Is there any way to force util.Secret to render the secret right away? When i do print(util.Secret('my_secret')) it just prints: "Secret('my_secret')"
<felixfontein> I don't think there is, IIRC fetching the actual value (IIRC it's called rendering) is an async function
<sint> How to print a secret right away then? I just wanna debug something.
<sint> I've updated a few things on my system and for some reason, Buildbot is not longer able to connect to the vault.
<cmouse> sint: try executing shell command that prints the secret
<cmouse> ShellCommand(util.Interpolate("echo %(secret:name)s"))
<sint> cmouse: Thanks. But still the same issue. HashiCorpVaultKvSecretProvider only gets permission denied. It was working perfectly for weeks. It works also perfectly with a simply test script using hvac.
<cmouse> hmm
<cmouse> sint: does your vault commands work
<sint> Ya, the vault seems to work fine. I can use the command line and it is even working if i copy the hvac code from the test script into my master.cfg. I am running everything on the same machine (Vault, master and a single worker).
<cmouse> sint: did you check vault logs?
<sint> not yet, but it's a good idea.
<sint> Vault logs not saying much. Even set to Debug mode and it's not saying anything about any kind of connection. I might try to run the hvac test code from within the worker in a build step.
koobs has joined #buildbot
antranigv has quit [Ping timeout: 240 seconds]
antranigv has joined #buildbot