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
{{ message }}
This repository has been archived by the owner on Nov 20, 2023. It is now read-only.
If you want to use TFE as a a private module registry right now the only option is to specify a remote backend, however in some circumstances one may want to use a non-remote (e.g. Azure, AWS, GCP) backend while still using a private module registry. An option should be added under advanced to facilitate this.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If you want to use TFE as a a private module registry right now the only option is to specify a remote backend, however in some circumstances one may want to use a non-remote (e.g. Azure, AWS, GCP) backend while still using a private module registry. An option should be added under advanced to facilitate this.
The text was updated successfully, but these errors were encountered: