Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-28 | 2 | -0/+78 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-27 | 1 | -0/+59 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-23 | 1 | -0/+70 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-21 | 1 | -0/+24 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-18 | 1 | -1/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-17 | 1 | -0/+56 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-15 | 2 | -0/+156 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-14 | 2 | -134/+23 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-10 | 2 | -0/+157 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-10 | 1 | -0/+21 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-07 | 1 | -0/+30 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-06 | 1 | -0/+54 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-20 | 1 | -0/+19 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-17 | 1 | -0/+67 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@masterogolowinski-master-patch-80898 | GitLab Bot | 2019-12-16 | 1 | -0/+30 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-10 | 1 | -0/+137 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-02 | 1 | -0/+50 |
| | |||||
* | Encrypt application settings with pre and post deployments | Arturo Herrero | 2019-11-26 | 1 | -2/+2 |
| | | | | | | | | | | | | | | | | | | | | | | | | We had concerns about the cached values on Redis with the previous two releases strategy: First release (this commit): - Create new encrypted fields in the database. - Start populating new encrypted fields, read the encrypted fields or fallback to the plaintext fields. - Backfill the data removing the plaintext fields to the encrypted fields. Second release: - Remove the virtual attribute (created in step 2). - Drop plaintext columns from the database (empty columns after step 3). We end up with a better strategy only using migration scripts in one release: - Pre-deployment migration: Add columns required for storing encrypted values. - Pre-deployment migration: Store the encrypted values in the new columns. - Post-deployment migration: Remove the old unencrypted columns | ||||
* | Encrypt application setting tokens | Arturo Herrero | 2019-11-26 | 1 | -0/+58 |
| | | | | | | | | | | | | | | This is the plan to encrypt the plaintext tokens: First release (this commit): 1. Create new encrypted fields in the database. 2. Start populating new encrypted fields, read the encrypted fields or fallback to the plaintext fields. 3. Backfill the data removing the plaintext fields to the encrypted fields. Second release: 4. Remove the virtual attribute (created in step 2). 5. Drop plaintext columns from the database (empty columns after step 3). | ||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-11-21 | 1 | -0/+56 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-11-19 | 1 | -0/+33 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-11-13 | 1 | -145/+0 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-11-12 | 1 | -0/+37 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-11-11 | 1 | -0/+34 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-11-08 | 1 | -0/+39 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-30 | 1 | -0/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-30 | 1 | -0/+55 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-24 | 1 | -0/+2 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-23 | 1 | -1/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-23 | 10 | -14/+14 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-22 | 1 | -0/+143 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-22 | 37 | -0/+74 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-10 | 1 | -0/+29 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-09 | 1 | -0/+63 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-30 | 1 | -0/+57 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-26 | 1 | -73/+0 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-24 | 1 | -0/+73 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-24 | 1 | -137/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-19 | 1 | -0/+37 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-18 | 1 | -63/+0 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-18 | 1 | -3/+3 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-17 | 1 | -0/+63 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-17 | 1 | -39/+0 |
| | |||||
* | Create self-monitoring project in background migration | Reuben Pereira | 2019-09-12 | 1 | -213/+0 |
| | | | | | - A regular migration caused problems such as https://gitlab.com/charts/gitlab/issues/1565. | ||||
* | Change discussion_ids on promoted epics notes | Alexandru Croitor | 2019-09-11 | 1 | -0/+81 |
| | | | | | | Notes on epics promoted from an issue used to get same discussion_id as the notes from the issue the epic was promoted from, which would cause problems when trying to reply to the epic discussion. | ||||
* | Added EncryptDeployTokensTokens spec file | Etienne BaquƩ | 2019-08-26 | 1 | -0/+47 |
| | |||||
* | Add a link to docs in project description | Reuben Pereira | 2019-08-23 | 1 | -0/+252 |
| | | | | Add to the service and migration both. | ||||
* | Migrations for adding issue_id to versions table | Luke Duncalfe | 2019-07-29 | 1 | -0/+38 |
| | | | | | | | | | | | | | | These migrations do the following: - Adds a new `issue_id` column to `versions`. This fixes an n+1 problem when loading versions for an issue in GraphQL as AR can now load from cache - Change the unique restraint on versions.sha to be scoped to `issue_id` as in order to import version data, we need to allow duplicate `sha` values for versions - Update all versions with an `issue_id` https://gitlab.com/gitlab-org/gitlab-ee/issues/11090 | ||||
* | Add default for outbound_local_requests_whitelist | Thong Kuah | 2019-07-25 | 1 | -0/+21 |
| | | | | It needs to default to an empty array logically. | ||||
* | Fix wrong pages access level default | Vladimir Shushlin | 2019-07-17 | 1 | -0/+97 |
| | | | | | - Set access level in before_validation hook - Add post migration for updating existing project_features |