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

[ZEPPELIN-3825] Allow custom service account for GCSNotebookRepo #3207

Closed
wants to merge 2 commits into from

Conversation

88sanjay
Copy link

What is this PR for?

The current implementation uses the default google applications service account to establish a connection with GCS. We cannot specify a custom service account for the connection with the existing implementation. This PR enables the same.

  • Added ZEPPELIN_NOTEBOOK_GCS_CREDENTIALS_FILE to ConfVars
  • Added functionality in GCSNotebookRepo and OldGCSNotebookRepo
    to get credentials from CREDENTIALS_FILE
  • Updated doc string and documentation

What type of PR is it?

[Improvement]

Todos

  • None

What is the Jira issue?

How should this be tested?

  • Create a new service account that has access to write to google cloud storage.
  • Disable Google Storage access to the default application service account.
  • Build and deploy zeppelin after updating zeppelin.notebook.gcs.credentialsJsonFilePath in zeppelin-site.xml
  • Validate that new notes are being written to GCS bucket

Screenshots (if appropriate)

  • None

Questions:

  • Does the licenses files need update? -No
  • Is there breaking changes for older versions? - No
  • Does this needs documentation? - Yes. Existing documentation has been updated to reflect the same.

* Added ZEPPELIN_NOTEBOOK_GCS_CREDENTIALS_FILE to ConfVars
* Added functionality in GCSNotebookRepo and OldGCSNotebookRepo
  to get credentials from CREDENTIALS_FILE
* Updated doc string and documentation
@88sanjay 88sanjay changed the title [ ZEPPELIN-3825 ] Allow custom service account for GCSNotebookRepo [ZEPPELIN-3825] Allow custom service account for GCSNotebookRepo Oct 23, 2018
@88sanjay 88sanjay closed this Oct 26, 2018
@88sanjay 88sanjay reopened this Oct 26, 2018
@88sanjay 88sanjay closed this Oct 26, 2018
@88sanjay 88sanjay reopened this Oct 26, 2018
@88sanjay 88sanjay closed this Oct 29, 2018
@88sanjay 88sanjay reopened this Oct 29, 2018
@88sanjay
Copy link
Author

88sanjay commented Nov 2, 2018

@zjffdu - Can you please review this change ?

@Leemoonsoo
Copy link
Member

Thanks @88sanjay for the contribution. Few problem on CI test has been fixed recently. Do you mind rebase your branch and see if this PR passes CI test just in case?

@88sanjay 88sanjay closed this Nov 5, 2018
@88sanjay 88sanjay reopened this Nov 5, 2018
@88sanjay 88sanjay closed this Nov 5, 2018
@88sanjay 88sanjay reopened this Nov 5, 2018
@88sanjay
Copy link
Author

88sanjay commented Nov 5, 2018

@Leemoonsoo looks like the Jenkins build passed.

@Leemoonsoo
Copy link
Member

@88sanjay Cool! LGTM

@88sanjay
Copy link
Author

88sanjay commented Nov 5, 2018

@Leemoonsoo I do not have access to merge

@asfgit asfgit closed this in 81e7030 Nov 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants