summaryrefslogtreecommitdiff
path: root/spec/controllers/projects/clusters_controller_spec.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-05-131-9/+26
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-04-241-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-04-211-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-04-191-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-03-311-6/+0
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-03-311-1/+22
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-02-171-5/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2023-02-171-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-12-221-4/+0
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-08-161-0/+12
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-05-261-144/+0
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-05-051-198/+0
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-03-071-0/+44
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-02-141-1/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-01-281-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-04-071-2/+12
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-12-021-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-09-291-0/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-09-021-14/+19
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-07-131-0/+12
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-07-071-0/+30
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-06-031-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-05-271-0/+7
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-04-301-3/+24
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-04-141-11/+66
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-311-4/+4
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-101-3/+0
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-281-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-191-0/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-121-27/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-271-17/+3
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-261-0/+32
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-131-0/+94
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-081-1/+51
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-021-3/+3
|
* Create new feature flagged UI for cloud providersEnrique Alcántara2019-09-091-2/+21
| | | | | | | - Create HAML UI select a cloud provider to create a cluster. - Add query param to :new cluster view to display a specific cluster provider form depending on the value of the provider query param. - Update unit tests and e2e tests to reflect these changes
* Enable project-level JIT resource creation60617-enable-project-cluster-jitTiger2019-06-181-2/+0
| | | | | | | | | | Previously this behaviour was only available to group and instance-level clusters, as some project clusters relied on Kubernetes credentials being passed through to the runner instead of having their resources managed by GitLab (which is not available when using JIT). These clusters have been migrated to unmanaged, so resources can be created on demand for the remaining managed clusters.
* Allow switching clusters between managed/unmanagedTiger2019-06-181-0/+4
| | | | | | Any resources created while the cluster was managed will be untouched, allowing users to set/unset this flag as they please.
* Add gitlab-managed option to clusters formMayra Cabrera2019-05-031-3/+32
| | | | | | | | When this option is enabled, GitLab will create namespaces and service accounts as usual. When disabled, GitLab wont create any project specific kubernetes resources Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56557
* Rename `ClusterPlatformConfigureWorker`George Tsiolis2018-12-211-2/+2
|
* Update specs to rails5 formatblackst0ne-convert-specs-rails5-styleblackst0ne2018-12-191-18/+24
| | | | | | | | | | Updates specs to use new rails5 format. The old format: `get :show, { some: params }, { some: headers }` The new format: `get :show, params: { some: params }, headers: { some: headers }`
* Only project clusters has Project Namespace fieldThong Kuah2018-11-081-2/+2
| | | | | Group clusters should not allow Project Namespace so don't show that field input too
* Extend clusters_controller for group type clustersThong Kuah2018-11-081-97/+51
| | | | | | | | | - Add pages javascripts to intialize clusters for group pages - Move specs asserting gcp specific validations from controller into UpdateService spec - Also teach Clusters::ApplicationController about groups
* Incorporates Kubernetes Namespace into Cluster's flowThong Kuah2018-11-021-0/+11
|
* Resolve controller sharing concernThong Kuah2018-11-011-0/+605
| | | | | | | | | | | | | | Use ClustersController as base while having Projects::ClustersController to inform what `clusterable` is. Thanks @ayufan for the great suggestion ! - View changes to work with new approach - Fix javascript for new approach - Fix feature specs for new approach - Fix QA
* Convert clusters to use a top-level controllerThong Kuah2018-11-011-594/+0
| | | | | | | | | | | | | | | | | | | | | | | | In preparation so that we can create both cluster attached to project and cluster attached to group. - Move ClustersController to top level - Move Clusters::ApplicationsController to top-level too - Creates a Clusters::BaseController to share common functions - Do not rely on @project ivar. Anything could set the ivar. - Fix Vue page components due to new data-page value Because of the controller change we have gone from `projects:clusters:new` to `clusters:new`, so we need to update the file location of the page components. There is somewhere a function that will convert data-page to a file location. On that note, projects/clusters/gcp/new/, translate to Projects::Clusters::Gcp#new doesn't exist so replace that with clusters/create_gcp/ and clusters/create_user/
* Revert back to go but use arguments for some casesThong Kuah2018-10-161-114/+99
| | | | | | It has been pointed out that `go` is used quite extensively so it's not an unknown idiam here at GitLab. And we have arguments with `go` which is a plus.
* Use subject in controller specThong Kuah2018-10-151-261/+202
| | | | | | | | Swap out `go` method with subject which is the convention. Re-organize 'PUT update' to remove un-necessary context nesting. DRY up repeated blocks to `add_maintainer` and `sign_in`
* Add FE option for users to choose to create a fully RBAC-enabled cluster or not.Thong Kuah2018-09-141-1/+15
| | | | This is similar to the option in the Add Existing cluster form
* Enable Kubernetes RBAC for GitLab Managed Apps for existing clustersThong Kuah2018-09-061-0/+32
|
View Lorry Controller Status