-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLOWarden applied team changes before a PR was approved. #261
Comments
This is something expected. As mentioned in the how it works section of the repository's readme file, there are CLOWarden includes a CLI tool that can assist with the initial setup. You can use the In any case, I'm sorry you run into some problems. We'll make this clearer in the README file (repository and chart) to help other users that may encounter the same issue. |
When we tried this in a separate org, it didn't remove existing teams -- you're just saying that there was some sort of, like, timing issue where the periodic reconciliation didn't happen because the service wasn't restarted? I think you should make this significantly more clear, yes, because it's not obvious at all. |
Periodic reconciliations happen every hour, so it could be indeed a timing issue. We'll do 👍 |
I'm confused, so anyone can send a PR to the repo and without us reviewing or approving it blow away all our org teams? the docs say:
|
No, changes proposed in a pull request need to be approved and merged. But this is not what caused this incident. The reason is that CLOWarden periodically ensures that the desired state as declared in the config file matches the current state in GitHub. The problem was that the config file used initially did not include all the resources available in GitHub. So when CLOWarden run a periodic reconciliation job (when it starts and every hour), it applied the necessary changes to make the desired state match the current. Unfortunately in this case, it deleted content. But it has nothing to do with the fact that a PR was created, that didn't matter. Using the CLI tool, you can always run a This is mentioned in a couple of places in the README file:
We also have a full section for the CLI tool in that README, and it's referenced from the Helm chart README as well. But in any case, we'll make this clearer, of course. |
Closes #261 Signed-off-by: Sergio Castaño Arteaga <[email protected]>
Closes #261 Signed-off-by: Sergio Castaño Arteaga <[email protected]>
See open-telemetry/community#2356
In short, we were testing CLOWarden for the OpenTelemetry organization. We were performing a staged rollout where we created a new team in the config file to make sure that we could slowly roll out CLOWarden to existing teams. Our expectation was that it would not touch items that weren't defined in the config file or that it wouldn't change anything until we merged the PR. What happened, though, is that existing teams in the organization were deleted while CLOWarden was checking the configuration.
I've attached the relevant log output of the clowarden server below.
The text was updated successfully, but these errors were encountered: