Piotr Galar
Piotr Galar
I know we have talked about different ideas to improve the json structure. Another idea may be to have a quick tool that one can run and answer "after these...
One has to manually run the sync workflow against the upgrade branch then.
We should notify CODEOWNERS about failing Apply. Alternatively, we could notify the person who merged the PR that initiated the Apply.
Two sets of credentials to manage fewer. TODO: check if there's anything secret in the tfstate (I don't think so but we should make sure).
Right now it shows up as a list of IDs which is not that useful.
When we transfer a repository, sync workflow fails in the source organisation. A run of clean workflow which removes the transferred repository from terraform state is required to fix that....
One for storing configuration only, and the other one for all the GitHub Actions responsible for applying the configuration changes. Hopefully, then we would be able to give out access...
It's really easy so let's document it so that anyone can do it.
Right now, a config like this will be accepted without raising an error: ``` members: admin: - galargh member: - galargh ``` The resulting application would give `galargh` only `member`...