-
Notifications
You must be signed in to change notification settings - Fork 28
Feature/raz #49
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
Feature/raz #49
Conversation
Signed-off-by: Nicolaie Marian <nmarian85@gmail.com>
Signed-off-by: Nicolaie Marian <nmarian85@gmail.com>
|
Wow, it worked :). Took me a moment to realize that the Author name and Signed-off-by field need to be the same. Github should document that feature better. |
| - polling_timeout | ||
| raz: | ||
| description: | ||
| - Flag indicating if Ranger RAZ fine grained access should be enabled for the datalake |
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.
Also should add entry for the response, which now includes enableRangerRaz
| payload.update(scale=self.scale) | ||
|
|
||
| if self.raz: | ||
| payload.update(enableRangerRaz=self.raz) |
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.
Not supported yet in GCP last time I checked, so will need a guard condition
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.
Need to add a guard condition for GCP deployments and update the general response fields to include the RAZ entry
|
Handled by #55 |
Somehow the DCO signed commits are giving me headaches. Retrying.