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

[BUG] Migrate security protos to SecurityContext #1722

Closed
2 tasks done
EngHabu opened this issue Oct 20, 2021 · 0 comments · Fixed by flyteorg/flyteadmin#305
Closed
2 tasks done

[BUG] Migrate security protos to SecurityContext #1722

EngHabu opened this issue Oct 20, 2021 · 0 comments · Fixed by flyteorg/flyteadmin#305
Assignees
Labels
bug Something isn't working flyteadmin Issue for FlyteAdmin Service untriaged This issues has not yet been looked at by the Maintainers

Comments

@EngHabu
Copy link
Contributor

EngHabu commented Oct 20, 2021

Describe the bug

Migrate AuthRole to SecurityContext so that clients can start migrating to using it...

Expected behavior

We should keep old and new protos in use until we officially delete the proto (after all clients migrate)

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@EngHabu EngHabu added bug Something isn't working untriaged This issues has not yet been looked at by the Maintainers flyteadmin Issue for FlyteAdmin Service labels Oct 20, 2021
@EngHabu EngHabu added this to the 0.18.2 milestone Oct 20, 2021
@EngHabu EngHabu modified the milestones: 0.18.2, 0.19.0 - Eagle Nov 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working flyteadmin Issue for FlyteAdmin Service untriaged This issues has not yet been looked at by the Maintainers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants