Skip to content
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

Replace Google only @kubeflow.org groups with @google.com groups #365

Closed
jlewi opened this issue Oct 24, 2020 · 4 comments
Closed

Replace Google only @kubeflow.org groups with @google.com groups #365

jlewi opened this issue Oct 24, 2020 · 4 comments

Comments

@jlewi
Copy link
Contributor

jlewi commented Oct 24, 2020

/kind area/process

Replace all @kubeflow.org groups that should contain only Googlers with @google.com addresses

@k8s-ci-robot
Copy link

@jlewi: The label(s) kind/area/process cannot be applied, because the repository doesn't have them

In response to this:

/kind area/process

Replace all @kubeflow.org groups that should contain only Googlers with @google.com addresses

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the labels:

Label Probability
kind/feature 0.63
area/engprod 0.91

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

@jlewi
Copy link
Contributor Author

jlewi commented Oct 24, 2020

[email protected] has been created
[email protected] has been deleted.

@jlewi
Copy link
Contributor Author

jlewi commented Oct 24, 2020

[email protected] has been deleted

[email protected] already exists

jlewi pushed a commit to jlewi/internal-acls that referenced this issue Oct 25, 2020
* This is a replacement for shelling out to GAM.

* Import all the existing groups to YAML files.
  * Get rid of the old text files and GAM code

Related to kubeflow#365 auto sync the Google groups

* Only import members for groups that already defined in GitHub
  * We don't want to be the ones putting people's emails into GitHub
  * As part of the migration we will ask members of groups not
    currently being auto-sync'd to open up PRs to add themselves
  * We will then enable AutoSync for all groups.

* Add code to upgrade specs
  * Add required users to all groups; e.g. the robot account.

* Support reading the OAuth2 credential from GCS
* Add a Makefile to make it easy to run the commands.
jlewi pushed a commit to jlewi/internal-acls that referenced this issue Oct 26, 2020
* This is a replacement for shelling out to GAM.

* Import all the existing groups to YAML files.
  * Get rid of the old text files and GAM code

* Only import members for groups that already defined in GitHub
  * We don't want to be the ones putting people's emails into GitHub
  * As part of the migration we will ask members of groups not
    currently being auto-sync'd to open up PRs to add themselves
  * We will then enable AutoSync for all groups.
  * We import stubs for all Groups but disable auto-sync; this way
    we can start asking people to submit PRs to join the group before
    we turn on the sync.

* Support reading the OAuth2 credential from GCS
* Add a Makefile to make it easy to run the commands.

* Use a content hash to detect when files have changed and determine when to resync.

* Also periodically force a resync so if there is any drift due to changes
  made outside the system they are reverted.

Related to kubeflow#365 auto sync the Google groups
k8s-ci-robot pushed a commit that referenced this issue Oct 28, 2020
* This is a replacement for shelling out to GAM.

* Import all the existing groups to YAML files.
  * Get rid of the old text files and GAM code

* Only import members for groups that already defined in GitHub
  * We don't want to be the ones putting people's emails into GitHub
  * As part of the migration we will ask members of groups not
    currently being auto-sync'd to open up PRs to add themselves
  * We will then enable AutoSync for all groups.
  * We import stubs for all Groups but disable auto-sync; this way
    we can start asking people to submit PRs to join the group before
    we turn on the sync.

* Support reading the OAuth2 credential from GCS
* Add a Makefile to make it easy to run the commands.

* Use a content hash to detect when files have changed and determine when to resync.

* Also periodically force a resync so if there is any drift due to changes
  made outside the system they are reverted.

Related to #365 auto sync the Google groups

Co-authored-by: Jeremy Lewi <[email protected]>
@jlewi jlewi closed this as completed Nov 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants