You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support early_auth_check flag in provider config. Closes #777
This change adds a new `early_auth_check` flag to the provider configuration.
It defaults to `true` which causes the provider to perform a dummy request to the GitLab API to verify the
configuration. If that is not desired it can be set to `false` which avoids this call.
This can be in useful if the GitLab instance is created within the same terraform module as this provider
is being used.
Copy file name to clipboardExpand all lines: docs/index.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,3 +74,8 @@ The following arguments are supported in the `provider` block:
74
74
*`client_cert` - (Optional) File path to client certificate when GitLab instance is behind company proxy. File must contain PEM encoded data.
75
75
76
76
*`client_key` - (Optional) File path to client key when GitLab instance is behind company proxy. File must contain PEM encoded data. Required when `client_cert` is set.
77
+
78
+
*`early_auth_check` - (Optional) (experimental) By default the provider does a dummy request to get the current user in order
79
+
to verify that the provider configuration is correct and the GitLab API is reachable.
80
+
Turn it off, to skip this check. This may be useful if the GitLab instance does not yet exist and is created within the same terraform module.
81
+
This is an experimental feature and may change in the future. Please make sure to always keep backups of your state.
0 commit comments