An error occurred fetching the project authors.
- 27 Jan, 2020 1 commit
-
-
Matt Kasa authored
- Encapsulate functionality for parsing and generating function URIs in Gitlab::Serverless::FunctionURI - Update references to Serverless with global scope operator - Delegate Serverless::DomainCluster#domain to PagesDomain Relates to https://gitlab.com/gitlab-org/gitlab/issues/195964
-
- 17 Dec, 2019 1 commit
-
-
GitLab Development authored
-
- 16 Dec, 2019 1 commit
-
-
James Fargher authored
Ran: bundle exec rubocop --only RSpec/EmptyLineAfterFinalLet -a \ spec/models/ spec/controllers/
-
- 13 Dec, 2019 1 commit
-
-
Alishan Ladhani authored
-
- 21 Nov, 2019 1 commit
-
-
João Cunha authored
- Tracks likst of api_groups instead of CRDs (much smaller) - Adds kubectl command to fetch api resources by api group - Adds kubectl command to delete api resources by api group - Adds/Updates specs
-
- 08 Oct, 2019 1 commit
-
-
Chris Baumbauer authored
-
- 22 Sep, 2019 1 commit
-
-
Matt Kasa authored
- Permits cloud_run parameter in ClustersController#create - Enables httpLoadBalancing, istioConfig, and cloudRunConfig in Gcp ProvisionService if cloud_run is enabled - Add `Enable Cloud Run on GKE` checkbox to cluster create page - Add `Enable Cloud Run on GKE` checkbox to cluster details - Default knative to pre_installed for cloud_run clusters - Make knative not uninstallable for pre_installd clusters - Update project clusters docs with entry about Cloud Run - Update tests and add new test for cluster with cloud_run enabled - Add Cloud Run on GKE strings to translations - Add spec that will fail when google-api-client has been upgraded - Add pre_installed to applications frontend - Pass providerType and preInstalledKnative to frontend - Display `installed via` on frontend for Cloud Run - Add Cloud Run spec for FinalizeCreationService Relates to https://gitlab.com/gitlab-org/gitlab/issues/27502
-
- 30 Aug, 2019 1 commit
-
-
Ash McKenzie authored
rails_helper.rb's only logic was to require spec_helper.rb.
-
- 29 Aug, 2019 1 commit
-
-
Ash McKenzie authored
rails_helper.rb's only logic was to require spec_helper.rb.
-
- 02 Aug, 2019 1 commit
-
-
João Cunha authored
-
- 31 Jul, 2019 1 commit
-
-
João Cunha authored
- After uninstalling the knative helm chart it's necessary to also remove some leftover resources to allow the cluster to be clean and knative to be reinstalleable. - Adds knative uninstall disclaimer - Uninstall ksvc before uninstalling knative Make list of Knative and Ingres resources explicit - To avoid deleting unwanted resources we are listing exact which resources will be deleted rather than simply deleting any resource that contains istio or knative words.
-
- 19 Jun, 2019 1 commit
-
-
Chris Baumbauer authored
-
- 04 Jun, 2019 1 commit
-
-
Jacques Erasmus authored
Remove Kn services cache from Clusters::Application::Knative Knative function can exist even if user did not installed Knative via GitLab managed apps. -> Move responsibility of finding services into the Cluster -> Responsability is inside Clusters::Cluster::KnativeServiceFinder -> Projects::Serverless::FunctionsFinder now calls depends solely on a cluster to find the Kn services. -> Detect Knative by resource presence instead of service presence -> Mock knative_installed response temporarily for frontend to develop Display loader while `installed === 'checking'` Added frontend work to determine if Knative is installed Memoize with_reactive_cache(*args, &block) to avoid race conditions When calling with_reactive_cache more than once, it's possible that the second call will already have the value populated. Therefore, in cases where we need the sequential calls to have consistent results, we'd fall under a race condition. Check knative installation via Knative resource presence Only load pods if Knative is discovered Always return a response in FunctionsController#index - Always indicate if Knative is installed, not installed or checking - Always indicate the partial response for functions. Final response is guaranteed when knative_installed is either true | false. Adds specs for Clusters::Cluster#knative_services_finder Fix method name when calling on specs Add an explicit check for functions Added an explicit check to see if there are any functions available Fix Serverless feature spec - we don't find knative installation via database anymore, rather via Knative resource Display error message for request timeouts Display an error message if the request times out Adds feature specs for when functions exist Remove a test purposed hardcoded flag Add ability to partially load functions Added the ability to partially load functions on the frontend Add frontend unit tests Added tests for the new frontend additions Generate new translations Generated new frontend translations Address review comments Cleaned up the frontend unit test. Added computed prop for `isInstalled`. Move string to constant Simplify nil to array conversion Put knative_installed states in a frozen hash for better read Pluralize list of Knative states Quey services and pods filtering name This way we don't need to filter the namespace in memory. Also, the data we get from the network is much smaller. Simplify cache_key and fix bug - Simplifies the cache_key by removing namespace duplicate - Fixes a bug with reactive_cache memoization
-
- 29 May, 2019 1 commit
-
-
João Cunha authored
Remove Kn services cache from Clusters::Application::Knative Knative function can exist even if user did not installed Knative via GitLab managed apps. -> Move responsibility of finding services into the Cluster -> Responsability is inside Clusters::Cluster::KnativeServiceFinder -> Projects::Serverless::FunctionsFinder now calls depends solely on a cluster to find the Kn services. -> Detect Knative by resource presence instead of service presence -> Mock knative_installed response temporarily for frontend to develop Display loader while `installed === 'checking'` Added frontend work to determine if Knative is installed Memoize with_reactive_cache(*args, &block) to avoid race conditions When calling with_reactive_cache more than once, it's possible that the second call will already have the value populated. Therefore, in cases where we need the sequential calls to have consistent results, we'd fall under a race condition. Check knative installation via Knative resource presence Only load pods if Knative is discovered Always return a response in FunctionsController#index - Always indicate if Knative is installed, not installed or checking - Always indicate the partial response for functions. Final response is guaranteed when knative_installed is either true | false. Adds specs for Clusters::Cluster#knative_services_finder Fix method name when calling on specs Add an explicit check for functions Added an explicit check to see if there are any functions available Fix Serverless feature spec - we don't find knative installation via database anymore, rather via Knative resource Display error message for request timeouts Display an error message if the request times out Adds feature specs for when functions exist Remove a test purposed hardcoded flag Add ability to partially load functions Added the ability to partially load functions on the frontend Add frontend unit tests Added tests for the new frontend additions Generate new translations Generated new frontend translations Address review comments Cleaned up the frontend unit test. Added computed prop for `isInstalled`. Move string to constant Simplify nil to array conversion Put knative_installed states in a frozen hash for better read Pluralize list of Knative states Quey services and pods filtering name This way we don't need to filter the namespace in memory. Also, the data we get from the network is much smaller. Simplify cache_key and fix bug - Simplifies the cache_key by removing namespace duplicate - Fixes a bug with reactive_cache memoization
-
- 30 Apr, 2019 1 commit
-
-
Thong Kuah authored
Only prometheus can be uninstalled atm, the rest will be dealt with later. Presumption is that new application types will have uninstallation implmemented at the same time.
-
- 17 Apr, 2019 2 commits
-
-
Chris Baumbauer authored
-
Chris Baumbauer authored
-
- 05 Apr, 2019 1 commit
-
-
Thong Kuah authored
- rewords examples starting with 'should' - rewords examples starting with 'it' Note: I had to manually fixup "onlies" to "only"
-
- 01 Apr, 2019 1 commit
-
-
Thong Kuah authored
Adds `# frozen_string_literal: true` to spec/models ruby files
-
- 28 Mar, 2019 1 commit
-
-
Chris Baumbauer authored
-
- 08 Mar, 2019 1 commit
-
-
Mayra Cabrera authored
This is a gitlab-ee port of the following gitlab-ce MR: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/25181
-
- 07 Mar, 2019 1 commit
-
-
walkafwalka authored
-
- 05 Mar, 2019 1 commit
-
-
João Cunha authored
- Creates new route - Creates new controller action - Creates call stack: Clusterss::ApplciationsController calls --> Clusters::Applications::UpdateService calls --> Clusters::Applications::ScheduleUpdateService calls --> ClusterUpdateAppWorker calls --> Clusters::Applications::PatchService --> ClusterWaitForAppInstallationWorker DRY req params Adds gcp_cluster:cluster_update_app queue Schedule_update_service is uneeded Extract common logic to a parent class (UpdateService will need it) Introduce new UpdateService Fix rescue class namespace Fix RuboCop offenses Adds BaseService for create and update services Remove request_handler code duplication Fixes update command Move update_command to ApplicationCore so all apps can use it Adds tests for Knative update_command Adds specs for PatchService Raise error if update receives an unistalled app Adds update_service spec Fix RuboCop offense Use subject in favor of go Adds update endpoint specs for project namespace Adds update endpoint specs for group namespace
-
- 15 Feb, 2019 1 commit
-
-
João Cunha authored
- Adds to specs the case where apps are also updated - Rename scope calls on Gitlab::UsageData and Clusters::Cluster - Removes a duplicated spec
-
- 07 Feb, 2019 1 commit
-
-
Thong Kuah authored
-
- 06 Feb, 2019 4 commits
-
-
Thong Kuah authored
All applications except for Jupyter have the same #set_initial_status, so create a new shared example which we include in all application specs except for juptyer_spec. Juptyer specs already have specs for it's version of #set_initial_status
-
Thong Kuah authored
All applications except for Jupyter have the same #set_initial_status, so create a new shared example which we include in all application specs except for juptyer_spec. Juptyer specs already have specs for it's version of #set_initial_status
-
Thong Kuah authored
This makes this consistent with :updated. And also avoids a potential issue where an install errors which means that that the recorded version won't necessarily reflect the version that is actually installed.
-
Thong Kuah authored
This makes this consistent with :updated. And also avoids a potential issue where an install errors which means that that the recorded version won't necessarily reflect the version that is actually installed.
-
- 10 Jan, 2019 1 commit
-
-
Chris Baumbauer authored
-
- 04 Jan, 2019 1 commit
-
-
Chris Baumbauer authored
-
- 03 Jan, 2019 1 commit
-
-
Chris Baumbauer authored
-
- 11 Dec, 2018 1 commit
-
-
Chris Baumbauer authored
-
- 06 Dec, 2018 1 commit
-
-
Dylan Griffith authored
-
- 26 Nov, 2018 1 commit
-
-
Chris Baumbauer authored
-
- 07 Nov, 2018 1 commit
-
-
Chris Baumbauer authored
-
- 06 Nov, 2018 2 commits
-
-
Chris Baumbauer authored
-
Chris Baumbauer authored
-
- 03 Nov, 2018 2 commits
-
-
Chris Baumbauer authored
-
Chris Baumbauer authored
-