Create cluster->Cluster provider switching ends in 400 if integration not configured with the selected provider
Summary
In my local GDK environment I have my AWS integration configured (not sure if there is a Google platform integration but couldn't find it). While I was in the process of creating a cluster, I tried to switch from Amazon to Google and I ended up in a 400 page.
Steps to reproduce
- Start your GDK instance.
- If there is a Google integration delete it.
- Go to a project with Auto DevOps enabled.
- Go to Operations -> Kubernetes.
- Click on Add Kubernetes cluster.
- Click on Amazon EKS. Click on Google GKE.
What is the current bug behavior?
You are directed to a 400 page.
What is the expected correct behavior?
You should get an information/error message on the screen explaining why the action is not available and if possible an action to help you fix it. For example:
The Google integration is not configured in your instance. |Configure integrations| or contact your Administrator
Relevant logs and/or screenshots
Results of GitLab environment info
GDK last updated: Updated as of 2020-03-11 12:42:20
Updating gitlab-workhorse to v8.24.0
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
) Command not found(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)