Denis Gukov
Denis Gukov
If needed we can create separate image based on `semaphoreui/semaphore`.
I'm understood why `cargo` needed (for arm). But building already too long. Let's leave thin image and extend it with full image if required. I planning to use this way...
Hi @zzecool thank you. I will reopen the issue. We need to fix it.
@hcderaad you don't need to recreate whole database, just update your access keys. But I don't think it is the same problem. `SEMAPHORE_ACCESS_KEY_ENCRYPTION` solves access keys problem but not Inventory.
@hcderaad is there any logs in Semaphore's output? This mean unexpected database restrictions was got. It can be result of database state or incorrect input fields.
Hi @MGertz did you solve the issue?
Hi @it-jelletruyers , @spomata it is not a bug, but not good UX. Fix change changed soon. Currently you need specify Matcher for each Integration.
Hi @kdjomeda does it work by using `ansible-playbook`? It is not looks like Semaphore issue because python was found correctly.
@kdjomeda in your setup description you use AWS profile `devops` but in Ansible you use profile `prod-uat-example`. Is it correct? Can you try `global_var_profile=devops` ?
Hm, it is really strange. @tboerger, @andreas-marschke do you have any idea?