fix: address prefix auto generated when subnets passed

[vburckhardt]

Description

fixes #676

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• If relevant, a test for the change is included or updated with this PR.
• If relevant, documentation for the change is included or updated with this PR.

For mergers

• Use a conventional commit message to set the release level. Follow the guidelines.
• Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
• Use the Squash and merge option.

[vburckhardt]

/run pipeline

[ocofaigh]

@vburckhardt As common-dev-assets was updated over the weekend renovate run, its now conflicting with your PR. If you locally rebase with main (git pull origin main) and run git submodule update --rebase to rebase the submodule, you should be good

[vburckhardt]

@ocofaigh - need a quick re approval after pulling dev tools (I think we should change the logic here to not require one - to be discussed)

[ocofaigh]

/run pipeline

[ocofaigh]

@vburckhardt Approved - will merge once pipeline passes.
FYI its not that you needed to bump the common-dev-assets, its the fact that you included an update to common-dev-assets in the initial commit which then became out of date with the one in main branch since renovate updated it. The best way to void the conflict is to avoid committing any updates to common-dev-assets and allow renovate to update it

[terraform-ibm-modules-ops]

🎉 This PR is included in version 7.13.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀