| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Current `auth.log` uses `fullpath` and `ip`, while `api_json.log` uses
`remote_ip` and `path` for the same fields. Let's standardize these
namings to make it easier for people working with the data.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66167
|
|
|
|
|
|
|
| |
API endpoints for requesting container repositories
and container repositories with their tag information
are enabled for users that want to specify the group
containing the repository rather than the specific project.
|
|
|
|
|
|
| |
Currently the base64-encoded value of the push-to-secondary data is
saved in `api_json.log`, and this can easily be hundreds of
megabytes. We should filter this from the logs.
|
|\
| |
| |
| |
| |
| |
| | |
Resolve "API support for group-level clusters"
Closes #55623
See merge request gitlab-org/gitlab-ce!30213
|
| |
| |
| |
| | |
This is basically a copy of the API for project clusters.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
New API endpoint for merge request count
Updates all open tabs at the same time with one call
Restructured API response
API response changed to 401 if no current_user
Added API + JS specs
Fix for Static Check
Updated Count on Open/Close, Assign/Unassign of MR's
Checking if MR Count is refreshed
Added # frozen_string_literal: true to spec
Added Changelog
|
|/
|
|
|
|
|
|
|
| |
This MR introduces tracking of the `rebase_jid` for merge requests. As
with `merge_ongoing?`, `rebase_in_progress?` will now return true if a
rebase is proceeding in sidekiq.
After one release, we should remove the Gitaly-based lookup of rebases.
It is much better to track this kind of thing via the database.
|
|
|
|
|
| |
The circuit breaker itself was removed in 11.5, this removes the
corresponding API endpoints which returned empty data since then.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Refactor api events class to use external helper
Move specs from old class
Add changelog and magic string
Refactor events class to be more explicit
Remove blank line
|
|
|
|
|
|
| |
The API get projects/:id/traffic/fetches allows user with write
access to the repository to get the number of clones for the
last 30 days.
|
|\
| |
| |
| |
| |
| |
| | |
API group labels
Closes #44901
See merge request gitlab-org/gitlab-ce!21368
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| | |
'master'
API: Support username with dots
Closes #51913
See merge request gitlab-org/gitlab-ce!24395
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Container repository cleanup API
Closes #55978
See merge request gitlab-org/gitlab-ce!24303
|
| |/
| |
| |
| |
| |
| | |
This includes a set of APIs to manipulate container registry.
This includes also an ability to delete tags based on requested
criteria, like keep-last-n, matching-name, older-than.
|
|/ |
|
|
|
|
| |
Authorize against release not project
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds the following initial CRUD endpoints for Clusters API:
- GET list of clusters
- GET specific cluster
- POST add existing cluster (mimic of "Add cluster")
- PUT update cluser
- DELETE destroy cluster
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/40473
|
|
|
|
|
|
|
|
|
|
|
| |
This commit introduces Releases API under /api/v4/projects/:id/releases
* We are introducing release policies at project level.
* We are deprecating releases changes from tags, both api and web
interface.
* Tags::CreateService no longer create a release
This feature is controlled by :releases_page feature flag
|
| |
|
|
|
|
|
|
|
|
| |
The Correlation ID is taken or generated from received X-Request-ID.
Then it is being passed to all executed services (sidekiq workers
or gitaly calls).
The Correlation ID is logged in all structured logs as `correlation_id`.
|
|\
| |
| |
| |
| | |
Fix API::Namespaces routing to accept namepaces with dots
See merge request gitlab-org/gitlab-ce!22912
|
| |
| |
| |
| |
| | |
It also renames the API::PROJECT_ENDPOINT_REQUIREMENTS constant to
API::NAMESPACE_OR_PROJECT_REQUIREMENTS
|
|/ |
|
|
|
|
|
|
|
|
|
|
| |
This new endpoint allow users to update a submodule's reference.
The MR involves adding a new operation RPC operation in gitaly-proto
(see gitlab-org/gitaly-proto!233) and change Gitaly to use this
new version (see gitlab-org/gitaly!936).
See gitlab-org/gitlab-ce!20949
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Partially addresses #47424.
Had to make changes to spec files because
stubbing methods on frozen objects is a mess
in RSpec and leads to failures:
https://github.com/rspec/rspec-mocks/issues/1190
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This mimics the same thing the RailsQueueDuration does for Rails controller
requests and will help diagnose issues with API delays.
Closes #46601
|
| |
|
|
|
|
|
|
|
|
|
|
| |
As described in https://github.com/aserafin/grape_logging/issues/45, if
a Grape error is caught by the handlers and a different return code
is returned, then the api_json.log would have a 500 error code
instead of the right value. Inserting the GrapeLogging middleware
after the Grape middleware fixes this problem.
Seen in https://gitlab.com/gitlab-com/infrastructure/issues/4249
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Add discussion API
See merge request gitlab-org/gitlab-ce!17510
|
| |
| |
| |
| |
| | |
* adds basic discussions API for issues and snippets
* reorganizes notes specs (so same tests can be used for all noteable types - issues, MRs, snippets)
|
|\ \
| | |
| | |
| | |
| | | |
# Conflicts:
# app/models/group.rb
# db/schema.rb
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Resolve "API endpoint for exporting project"
Closes #29130
See merge request gitlab-org/gitlab-ce!15860
|
| | |/ |
|
| |/ |
|
|/ |
|
| |
|
| |
|
| |
|