gitlab-org--gitlab-foss/app/workers/cluster_project_configure_worker.rb

# frozen_string_literal: true

class ClusterProjectConfigureWorker
  include ApplicationWorker
  include ClusterQueue

  def perform(project_id)
    return if Feature.enabled?(:ci_preparing_state, default_enabled: true)

    project = Project.find(project_id)

    ::Clusters::RefreshService.create_or_update_namespaces_for_project(project)
  end
end
Create k8s namespace for project in group clusters AFAIK the only relevant place is Projects::CreateService, this gets called when user creates a new project, forks a new project and does those things via the api. Also create k8s namespace for new group hierarchy when transferring project between groups Uses new Refresh service to create k8s namespaces - Ensure we use Cluster#cluster_project If a project has multiple clusters (EE), using Project#cluster_project is not guaranteed to return the cluster_project for this cluster. So switch to using Cluster#cluster_project - at this stage a cluster can only have 1 cluster_project. Also, remove rescue so that sidekiq can retry 2018-11-15 04:17:41 -05:00			`# frozen_string_literal: true`

			`class ClusterProjectConfigureWorker`
			`include ApplicationWorker`
			`include ClusterQueue`

			`def perform(project_id)`
Add feature flag for build preparing state The flag is on by default, but allows us to revert back to the old behaviour if we encounter any problems. 2019-03-12 02:37:37 -04:00			`return if Feature.enabled?(:ci_preparing_state, default_enabled: true)`

Create k8s namespace for project in group clusters AFAIK the only relevant place is Projects::CreateService, this gets called when user creates a new project, forks a new project and does those things via the api. Also create k8s namespace for new group hierarchy when transferring project between groups Uses new Refresh service to create k8s namespaces - Ensure we use Cluster#cluster_project If a project has multiple clusters (EE), using Project#cluster_project is not guaranteed to return the cluster_project for this cluster. So switch to using Cluster#cluster_project - at this stage a cluster can only have 1 cluster_project. Also, remove rescue so that sidekiq can retry 2018-11-15 04:17:41 -05:00			`project = Project.find(project_id)`

Shift to class methods for RefreshService As we don't use any instance attributes and we don't seem to have any commonalities between the cluster and the project variant. 2018-12-04 17:57:02 -05:00			`::Clusters::RefreshService.create_or_update_namespaces_for_project(project)`
Create k8s namespace for project in group clusters AFAIK the only relevant place is Projects::CreateService, this gets called when user creates a new project, forks a new project and does those things via the api. Also create k8s namespace for new group hierarchy when transferring project between groups Uses new Refresh service to create k8s namespaces - Ensure we use Cluster#cluster_project If a project has multiple clusters (EE), using Project#cluster_project is not guaranteed to return the cluster_project for this cluster. So switch to using Cluster#cluster_project - at this stage a cluster can only have 1 cluster_project. Also, remove rescue so that sidekiq can retry 2018-11-15 04:17:41 -05:00			`end`
			`end`