summaryrefslogtreecommitdiff
path: root/lib/api/internal.rb
Commit message (Collapse)AuthorAgeFilesLines
* Record and show last used date of SSH KeysVincent Wong2017-01-091-1/+7
| | | | | | | | Addresses: Issue #13810 1. Adds a last_used_at attribute to the Key table/model 2. Update a key's last_used_at whenever it gets used 3. Display how long ago an ssh key was last used
* Accept environment variables from the `pre-receive` script.Timothy Andrew2016-12-161-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. Starting version 2.11, git changed the way the pre-receive flow works. - Previously, the new potential objects would be added to the main repo. If the pre-receive passes, the new objects stay in the repo but are linked up. If the pre-receive fails, the new objects stay orphaned in the repo, and are cleaned up during the next `git gc`. - In 2.11, the new potential objects are added to a temporary "alternate object directory", that git creates for this purpose. If the pre-receive passes, the objects from the alternate object directory are migrated to the main repo. If the pre-receive fails the alternate object directory is simply deleted. 2. In our workflow, the pre-recieve script (in `gitlab-shell) calls the `/allowed` endpoint, which calls out directly to git to perform various checks. These direct calls to git do _not_ have the necessary environment variables set which allow access to the "alternate object directory" (explained above). Therefore these calls to git are not able to access any of the new potential objects to be added during this push. 3. We fix this by accepting the relevant environment variables (GIT_ALTERNATE_OBJECT_DIRECTORIES, GIT_OBJECT_DIRECTORY) on the `/allowed` endpoint, and then include these environment variables while calling out to git. 4. This commit includes (whitelisted) these environment variables while making the "force push" check. A `Gitlab::Git::RevList` module is extracted to prevent `ForcePush` from being littered with these checks.
* Fix POST /internal/allowed to cope with gitlab-shell v4.0.0 project pathsNick Thomas2016-11-161-36/+2
| | | | | | | | | | | | | gitlab-shell v3.6.6 would give project paths like so: * namespace/project gitlab-shell v4.0.0 can give project paths like so: * /namespace1/namespace2/project * /namespace/project * /path/to/repository/storage/namespace1/namespace2/project * /path/to/repository/storage/namespace/project
* Refactor storage path extraction from full repo pathdz-internal-api-fullpathDmitriy Zaporozhets2016-10-281-6/+1
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Make internal api work with full repo path instead of nameDmitriy Zaporozhets2016-10-271-4/+14
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Handle LFS token creation and retrieval in the same method, and in the same ↵lfs-ssh-authorization-fixPatricio Cano2016-09-281-1/+1
| | | | | | Redis connection. Reset expiry time of token, if token is retrieved again before it expires.
* Revert "Revert all changes introduced by ↵lfs-supportKamil Trzcinski2016-09-191-0/+13
| | | | | | https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6043" This reverts commit 6d43c95b7011ec7ec4600e00bdc8df76bb39813c.
* Revert all changes introduced by ↵Kamil Trzcinski2016-09-191-13/+0
| | | | https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6043
* Rename capabilities to authentication_abilitiesKamil Trzcinski2016-09-161-3/+3
|
* Merge remote-tracking branch 'origin/lfs-support-for-ssh' into per-build-tokenKamil Trzcinski2016-09-151-0/+13
|\ | | | | | | | | | | | | | | # Conflicts: # app/controllers/projects/git_http_client_controller.rb # app/helpers/lfs_helper.rb # lib/gitlab/auth.rb # spec/requests/lfs_http_spec.rb
| * Better authentication handling, syntax fixes and better actor handling for ↵Patricio Cano2016-09-151-8/+1
| | | | | | | | LFS Tokens
| * Refactored handling of the `LfsToken` and added functionality to it to ↵Patricio Cano2016-09-151-9/+11
| | | | | | | | simplify external code.
| * Refactored LFS auth logic when using SSH to use its own API endpoint ↵Patricio Cano2016-09-151-12/+18
| | | | | | | | `/lfs_authenticate` and added tests.
| * Refactor LFS token logic to use a Redis key instead of a DB field, making it ↵Patricio Cano2016-09-151-4/+5
| | | | | | | | a 1 use only token.
| * Added LFS support to SSHPatricio Cano2016-09-151-1/+12
| | | | | | | | - Required on the GitLab Rails side is mostly authentication and API related.
* | Fix existing authorization specsKamil Trzcinski2016-09-151-10/+8
| |
* | Add access specsKamil Trzcinski2016-09-151-2/+12
|/
* Minor edits to two_factor_recovery_codes API error catchingDrew Blessing2016-08-311-5/+9
|
* Add two factor recovery endpoint to internal APIDrew Blessing2016-08-241-0/+25
|
* api for generating new merge requestScott Le2016-08-111-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | DRY code + fix rubocop Add more test cases Append to changelog DRY changes list find_url service for merge_requests use GET for getting merge request links remove files rename to get_url_service reduce loop add test case for cross project refactor tiny thing update changelog
* Fix a bug where the project's repository path was returned instead of the ↵19842-cloning-a-gitlab-wiki-returns-the-repo-not-the-repo-s-wikiAlejandro Rodríguez2016-07-151-1/+6
| | | | wiki path
* Only allow Git Access on the allowed protocolPatricio Cano2016-07-051-2/+5
|
* Refactor repository paths handling to allow multiple git mount pointsAlejandro Rodríguez2016-06-291-11/+25
|
* Remove explicit Gitlab::Metrics.action assignments, are already automatic.18760-remove-explicate-assignment-on-metrics-actionPaco Guzman2016-06-181-2/+0
|
* Fix setting of "action" for Grape transactionsYorick Peterse2016-04-201-1/+1
| | | | | | | Merely setting the "action" tag will only result in the transaction itself containing a value for this tag. To ensure other metrics also contain this tag we must set the action using Transaction#action= instead.
* Add "action" tag to /internal/allowed APIYorick Peterse2016-04-181-2/+4
| | | | | This allows us to re-use any other analytics that rely on the "action" tag having a value set.
* updated internal.rb and spec based on MR feedbackJames Lopez2016-02-261-3/+3
|
* fix for projects ending in .wikiJames Lopez2016-02-241-1/+8
|
* Improve Git access error messages.Douwe Maan2015-05-131-19/+7
|
* Respond with full GitAccess error if user has project read access.api-internal-errorsDouwe Maan2015-03-241-1/+1
|
* Refactor GitAccess to use instance variables.Douwe Maan2015-03-241-19/+17
|
* Don't leak information about private project existence via Git-over-SSH/HTTP.Douwe Maan2015-03-021-17/+22
|
* Improve broadcast message APIDmitriy Zaporozhets2015-02-181-0/+2
|
* Dont send 404 if no broadcast messages now because it flood gitlab-shell ↵Dmitriy Zaporozhets2015-02-181-2/+0
| | | | logs with 404 errors :(
* Add internal broadcast message API.Douwe Maan2015-02-071-0/+8
|
* Avoid using {...} for multi-line blocksDmitriy Zaporozhets2015-02-021-3/+1
|
* Replace regex methods by string ones since fasterCiro Santilli2014-12-281-2/+2
| | | | and more readable.
* Fix internal API for missing project or keyDmitriy Zaporozhets2014-12-011-4/+9
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Better message for failed pushes because of git hooksValery Sizov2014-11-181-1/+1
| | | | | | Conflicts: lib/gitlab/git_access.rb spec/lib/gitlab/git_access_spec.rb
* add gitlab-shell identificationValery Sizov2014-10-151-0/+4
|
* Improve wiki path parsing in internal apiDmitriy Zaporozhets2014-10-071-1/+1
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Developers can push to wiki repo. Protected branches does not affect wiki ↵Dmitriy Zaporozhets2014-10-071-3/+10
| | | | | | repo any more Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Make sure /api/allowed return 200 status codeDmitriy Zaporozhets2014-09-031-0/+2
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* /api/allowed use POST nowDmitriy Zaporozhets2014-09-031-1/+1
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Rewrite GitAccess for gitlab-shell v2Dmitriy Zaporozhets2014-09-011-4/+1
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Dont expose user email via APIDmitriy Zaporozhets2014-06-131-1/+0
| | | | | | | | | | | | | To prevent leaking of users info we reduce amount of user information retrieved via API for normal users. What user can get via API: * if not admin: only id, state, name, username and avatar_url * if admin: all user information * about himself: all informaion Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* first setup to protect protected branched to force updatesSteven Thonus2014-03-251-1/+3
|
* Use GitAccess in internal apiDmitriy Zaporozhets2014-03-201-41/+19
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Add ldap check in application_controller and internal apiDmitriy Zaporozhets2014-03-101-1/+7
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* In the case when a user can and has authenticated with ldap, howeverJurnell Cockhren2014-01-281-1/+3
| | | | | ldap is disabled in the gitlab config, this fixes the API still calling the ldap backend.
View Lorry Controller Status