-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix!: Don't provide defaults for public repositories (#34)
- Loading branch information
Showing
3 changed files
with
36 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# Upgrading to v0.3.0 | ||
|
||
The v0.3.0 release of **terraform-google-artifact-registry** is a backwards | ||
incompatible release. | ||
|
||
### Defaults for Public Repositories | ||
|
||
Previously, this module provided defaults that pointed at well-known public | ||
repositories. Previously, for example, you could specify remote repository | ||
configuration for Docker Hub like so: | ||
|
||
``` | ||
remote_repository_config = { | ||
docker_repository = {} | ||
} | ||
``` | ||
|
||
And you would get a remote repository configuration that would point to Docker | ||
Hub. Now, you have to explicitly specify that you want Docker Hub like so: | ||
|
||
``` | ||
remote_repository_config = { | ||
docker_repository = { | ||
public_repository = "DOCKER_HUB" | ||
} | ||
} | ||
``` | ||
|
||
This change was made because the previous behavior of defaulting these to | ||
well-known values turned out to be incompatible with specifying custom | ||
repository options via the `custom_repository` argument. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters