You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@datalab.apache.org by "Vira Vitanska (Jira)" <ji...@apache.org> on 2022/05/27 08:14:00 UTC
[jira] [Updated] (DATALAB-2796) [TPCP] Investigate git credentials storing and connection with ungit
[ https://issues.apache.org/jira/browse/DATALAB-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vira Vitanska updated DATALAB-2796:
-----------------------------------
Sprint: Apache DataLab release 2.6.1 (was: Apache DataLab release 2.6)
> [TPCP] Investigate git credentials storing and connection with ungit
> --------------------------------------------------------------------
>
> Key: DATALAB-2796
> URL: https://issues.apache.org/jira/browse/DATALAB-2796
> Project: Apache DataLab
> Issue Type: Task
> Security Level: Public(Regular Issues)
> Components: DataLab Main
> Reporter: Vira Vitanska
> Assignee: Leonid Frolov
> Priority: Major
> Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat, TPCP
> Attachments: Git in terminal.txt
>
>
> # Investigate what information is transferred to ungit during git credentials adding in order to find out the chain of connection. There is a case when several users use the same VM and links to JupyterUI/ungit. In this situation all changes are wrote by user who had created instance, but not from user who really had made changes.
> # Investigate how to store git credential in secure way on WM. Now they are stored in hidden folder in open way which are visible who has link to VM.
> # Investigate how transfer git credentials in secure way in IDE (Jupyter UI) in code.
> # After adding git credentials in Jupyter terminal I could not push changes:
> {code:java}
> datalab-user@ip-172-31-50-180:~/demo_aws_snowflake$ git status
> On branch master
> Your branch is up to date with 'origin/master'.Untracked files:
> (use "git add <file>..." to include in what will be committed)
> Scala_data_preparation.jsonnothing added to commit but untracked files present (use "git add" to track)
> datalab-user@ip-172-31-50-180:~/demo_aws_snowflake$ git add -A
> datalab-user@ip-172-31-50-180:~/demo_aws_snowflake$ git status
> On branch master
> Your branch is up to date with 'origin/master'.Changes to be committed:
> (use "git restore --staged <file>..." to unstage)
> new file: Scala_data_preparation.jsondatalab-user@ip-172-31-50-180:~/demo_aws_snowflake$ git commit -m 'test'
> datalab-user@ip-172-31-50-180:~/demo_aws_snowflake$ git status
> On branch master
> Your branch is up to date with 'origin/master'.Changes to be committed:
> (use "git restore --staged <file>..." to unstage)
> new file: Scala_data_preparation.jsondatalab-user@ip-172-31-50-180:~/demo_aws_snowflake$ git push origin/master
> fatal: 'origin/master' does not appear to be a git repository
> fatal: Could not read from remote repository.Please make sure you have the correct access rights
> and the repository exists.
> datalab-user@ip-172-31-50-180:~/demo_aws_snowflake$ git push
> Everything up-to-date
> datalab-user@ip-172-31-50-180:~/demo_aws_snowflake$ git push origin
> Everything up-to-date
> datalab-user@ip-172-31-50-180:~/demo_aws_snowflake$ git push origin master
> Everything up-to-date
> datalab-user@ip-172-31-50-180:~/demo_aws_snowflake$ git config --list
> user.name=Example User
> user.email=example@example.com
> init.templatedir=/home/datalab-user/.git/templates
> core.excludesfile=/home/datalab-user/.gitignore
> http.proxy=http://ec2-3-72-116-155.eu-central-1.compute.amazonaws.com:3128
> https.proxy=http://ec2-3-72-116-155.eu-central-1.compute.amazonaws.com:3128
> core.repositoryformatversion=0
> core.filemode=true
> core.bare=false
> core.logallrefupdates=true
> remote.origin.url=https://gitlab.com/accountdemo1/demo_aws_snowflake.git
> remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
> branch.master.remote=origin
> branch.master.merge=refs/heads/master
> user.name=demo
> user.email=demo@epam.co {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@datalab.apache.org
For additional commands, e-mail: dev-help@datalab.apache.org