1. 02 Apr, 2019 1 commit
  2. 25 Mar, 2019 1 commit
  3. 20 Mar, 2019 1 commit
  4. 08 Mar, 2019 1 commit
  5. 07 Mar, 2019 1 commit
  6. 06 Mar, 2019 6 commits
  7. 05 Mar, 2019 3 commits
    • João Cunha's avatar
      Rename ClusterUpdateAppWorker to ClusterPatchAppWorker · 3bdff7aa
      João Cunha authored
      - This is to avoid colision with EE ClusterUpdateAppWorker
      3bdff7aa
    • João Cunha's avatar
      Creates Clusterss::ApplciationsController update endpoint · f8234d9a
      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
      f8234d9a
    • Gabriel Mazetto's avatar
      Skip project validation when switching storage layouts · b4f20502
      Gabriel Mazetto authored
      This is a fix for the Hashed Storage migration and Rollback procedure
      to ignore any project-level validation error that can happen in a
      long-running instance.
      
      There are many situations where defaults and acceptable values changed
      but, because we didn't provide a migration to "valid" attributes, it
      can happen that project will not be `valid? => true`.
      
      Because the changes we are making are limited to setting a project as
      read_only or changing the storage_level, it's safe to bypass validation.
      b4f20502
  8. 04 Mar, 2019 1 commit
  9. 02 Mar, 2019 1 commit
  10. 01 Mar, 2019 11 commits
  11. 27 Feb, 2019 5 commits
  12. 26 Feb, 2019 5 commits
  13. 25 Feb, 2019 3 commits