`terraform apply` wants to destroy and recreate the pull mirrors
Summary
Customer (SFDC internal only) reported they are using GitLab terraform provider to set up pull mirrors into Gitlab from GitHub.
The bug they are encountering is "every time we 'terraform apply' it wants to destroy and recreate the pull mirror.
Customer found a similar bug for push mirrors was fixed a year go and suspects similar cause for pull mirrors.
"A similar bug for push mirrors was fixed a year ago.
The fix for push mirrors uses a DiffSuppressFunc before comparing the redacted password returned by GitLab with the terraform user’s password.
pull mirrors use import_url
, which has no DiffSuppressFunc. That is the likely cause of the spurious diff that we observe - the pull mirror compares GitLab API’s redacted password with the actual password in our terraform, and always finds a difference."
Customer has a workaround but would like this bug to be fixed to remove their workaround.
Steps to reproduce
What is the current bug behavior?
When the customer terraform apply
it wants to destroy and recreate the pull mirror
What is the expected correct behavior?
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
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
)(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)