-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update terraform-module #528
Conversation
/run pipeline |
8cbf041
to
79b5b10
Compare
/run pipeline |
79b5b10
to
ba459e4
Compare
/run pipeline |
ba459e4
to
c11cd03
Compare
/run pipeline |
1 similar comment
/run pipeline |
c11cd03
to
bf934a3
Compare
/run pipeline |
1 similar comment
/run pipeline |
@toddgiguere @shemau The test failed with:
As codeowners could you take a look, as this blocks us from merging #532 which has the update to move to tf 1.6.6 |
…into vpc and vpe modules
The bump to landing-zone-vpc changed how the module output the vpc.name. The actual error followed the snippet above │ The "for_each" map includes keys derived from resource attributes that
│ cannot be determined until apply, and so Terraform cannot determine the
│ full set of keys that will identify the instances of this resource.
│
│ When working with unknown values in for_each, it's better to define the map
│ keys statically in your configuration and place apply-time results only in
│ the map values.
│ The vpc_name may now be generated by the module and becomes derived during the apply. The default example was not impacted, because it passes the same name to both the VPC module and the VPE module. This is not the most elegant solution, since the module can prefix/extend the name, so technically it is not the VPC name. However, it works, because we then use the name without prefix for the names of the gateways and reserved IPs. This is still enough to identify them. The main module is not changing, so there is no risk of regression/change. |
… string into vpc and vpe modules" This reverts commit c8827cc.
@shemau Lets update to |
/run pipeline |
Postgres install failed with:
Going to retry.. |
/run pipeline |
Hmm, upgrade test failed with:
@shemau are we expecting this, or know why its happening? |
I was not expecting that. 7.18.0 to 7.18.2 should only have been adding a delay and a new data source. I will dig into the logs, but will probably run the test again. |
/run pipeline |
/run pipeline |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
/run pipeline |
I have reverted the VPC module update to see if pipeline passes |
/run pipeline |
/run pipeline |
So even after removing the the VPC update from this PR, the same error occurs:
Since its unrelated to the module, and just updates to the examples, I'm going to add back newer vpc version, and skip upgrade test |
/run pipeline |
🎉 This PR is included in version 4.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This PR contains the following updates:
3.12.0
->3.14.0
7.18.0
->7.18.2
Release Notes
terraform-ibm-modules/terraform-ibm-icd-postgresql (terraform-ibm-modules/icd-postgresql/ibm)
v3.14.0
Compare Source
Features
v3.13.1
Compare Source
Bug Fixes
v3.13.0
Compare Source
Features
log_disconnections
andlog_connections
in theconfiguration
input variable object (#421) (57d9068)terraform-ibm-modules/terraform-ibm-landing-zone-vpc (terraform-ibm-modules/landing-zone-vpc/ibm)
v7.18.1
Compare Source
Bug Fixes
vpc_data
is always output after initial apply (#781) (069d418)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.