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
Use the rbac API when creating and deleting policy #556
Conversation
|
Changes Unknown when pulling 145fe5a on rthallisey:rbac-api into ** on openshift:master**. |
|
Changes Unknown when pulling 8db28ad on rthallisey:rbac-api into ** on openshift:master**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you could have a separate PR for the vendor stuff, that would be fantastic. Tough to see the meaningful changes when 269 files are involved.
|
Changes Unknown when pulling 9876882 on rthallisey:rbac-api into ** on openshift:master**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
VISACK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
@djzager @shawn-hurley I made a bunch of changes since your reviews. Going to leave the do-not-merge tag around until you get a chance to review it again. |
|
Changes Unknown when pulling 9c7c5a4 on rthallisey:rbac-api into ** on openshift:master**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CONDACK, want to discuss the thoughts that I had.
pkg/apb/svc_acct.go
Outdated
| } | ||
|
|
||
| return rFilePath, nil | ||
| p := runtime.Provider{Log: s.log} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the runtime provider just be an apb package variable? Also, should we remove this function and just call the provider from the execute APB? These are just thoughts, all around this looks good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that the runtime var should be an available variable and it needs to be wherever we make cluster calls. I haven't figured out yet how I'm going to approach providing it yet. You're ahead of the game :).
Agree that this function doesn't need to be called. All the guts are now in the runtime pkg.
|
Changes Unknown when pulling acf58e2 on rthallisey:rbac-api into ** on openshift:master**. |
|
Changes Unknown when pulling 2224602 on rthallisey:rbac-api into ** on openshift:master**. |
|
Changes Unknown when pulling b1aab44 on rthallisey:rbac-api into ** on openshift:master**. |
|
Changes Unknown when pulling bd9395f on rthallisey:rbac-api into ** on openshift:master**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK
* Use the rbac API when creating policy * Use the client pkg to hide some of the resource creation * Add the runtime pkg for additional abstraction * Fix tests * Distribute provide variable * Use the api to destroy the apb sandbox * Add destroysandbox to the fake provider
Describe what this PR does and why we need it:
Use the rbac API to create Roles.
Changes proposed in this pull request
depends-on: #561
depends-on: #562
Partially-fixes: #233