This repository has been archived by the owner on Sep 16, 2020. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WHY?
With use of terraforming-aws for infrastructure paving, one important part which is missing from terraform output file is reserved IPs for each subnet. If reserved IPs are not in network config, BOSH will try to pick the very first IP and fail as it is reserved.
As per AWS VPC documentation, First 4 IPs are reserved in each subnet.
CHANGES
cidrhost
function for subnets.Output will look something like this:
Similarly for other subnets.
How this was used?
This was used to automate opsmanager deployment by fetching properties like
reference: config link