d3866fb48c
If the service fails mid-point, then we should be able to re-run this service. So, detect presence of any previously created Kubernetes resource and update or create accordingly. Fix specs accordingly. In the case of finalize_creation_service_spec.rb, I decided to stub out the async worker rather than maintaining individual stubs for various kubeclient calls for that worker. |
||
|---|---|---|
| .. | ||
| api | ||
| backup | ||
| banzai | ||
| bitbucket | ||
| bitbucket_server | ||
| constraints | ||
| container_registry | ||
| gitaly | ||
| gitlab | ||
| google_api | ||
| json_web_token | ||
| mattermost | ||
| microsoft_teams | ||
| object_storage | ||
| omni_auth/strategies | ||
| quality | ||
| rspec_flaky | ||
| system_check | ||
| after_commit_queue_spec.rb | ||
| event_filter_spec.rb | ||
| expand_variables_spec.rb | ||
| extracts_path_spec.rb | ||
| feature_spec.rb | ||
| file_size_validator_spec.rb | ||
| forever_spec.rb | ||
| gitlab_spec.rb | ||
| milestone_array_spec.rb | ||
| system_check_spec.rb | ||
| uploaded_file_spec.rb | ||