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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,15 @@ Extending the adopted spec, each change should have a link to its corresponding
8
8
9
9
## [Unreleased]
10
10
11
+
## [5.0.0] - 2019-11-04
12
+
13
+
5.0.0 is a backwards incompatible release for `modules/fabric-project`. See the [upgrade guide](./docs/upgrading_to_fabric_project_v5.0.md) for details.
14
+
15
+
### Fixed
16
+
17
+
- Manage service activation in `modules/fabric-project` with a resource instead of relying on `modules/project-services`, so that output dependency on services works again. Fixes [#308]. [#309]
18
+
19
+
11
20
## [4.0.1] - 2019-10-30
12
21
13
22
### Fixed
@@ -217,7 +226,8 @@ Extending the adopted spec, each change should have a link to its corresponding
217
226
### ADDED
218
227
- This is the initial release of the Project Factory Module.
For each of the above resources, issue a `terraform state mv` command, where the destination resource omits `module.project_services`. Using the example above:
Once done, test that `terraform plan` won't create or destroy any `google_project_service` resource, then delete the `terraform-state.json` file you saved earlier.
46
+
47
+
In case of issues, revert the module version, run `terraform init`, then revert to the known working Terraform state version with `terraform state push terraform-state.json`.
0 commit comments