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

[Enhancement] Remove service account code in main #2005

Closed
derek-ho opened this issue Jun 13, 2024 · 2 comments · Fixed by #2041
Closed

[Enhancement] Remove service account code in main #2005

derek-ho opened this issue Jun 13, 2024 · 2 comments · Fixed by #2041
Assignees
Labels
enhancement New feature or request triaged

Comments

@derek-ho
Copy link
Collaborator

Is your feature request related to a problem?
If there is no plan to backport service accounts feature to 2.x, then the code should be removed. Because of this difference, code that touches user pages may conflict on the backport, leading to manual backports and misses during reviews (including recent autocut for 2.15 release).
What solution would you like?
Removal of service accounts code to consolidate main and 2.x, if there is no plan to release
What alternatives have you considered?
None
Do you have any additional context?
None

@derek-ho derek-ho added enhancement New feature or request untriaged labels Jun 13, 2024
@derek-ho
Copy link
Collaborator Author

Related issue: #1999

@stephen-crawford
Copy link
Contributor

[Triage] Hi @derek-ho, for filing this issue. This seems like a good request since we are not currently looking at moving Service Accounts back to 2.x. Will mark as triaged.

@stephen-crawford stephen-crawford changed the title [RFC] Remove service account code in main [Enhancement] Remove service account code in main Jun 17, 2024
@derek-ho derek-ho self-assigned this Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants