feat: support all private PowerVS CIDRs in ACL rule; change name of DCs in Dropwdown for DAs; fix nfs

[surajsbharadwaj]

Description

• Support all private PowerVS CIDRs in ACL rule;
• Import any number of PowerVS images , and now parallely
• clean_default_sg_acl included in the landing zone preset to clean the default sg rule for new deployments
• Upgrade to ibm-sles-15-4-amd64-sap-applications-6 & ibm-redhat-8-6-amd64-sap-applications-4 on intel VSI landing zone for new deployments. Will not affect the previous DA version
• All DAs now use terraform-ibm-modules/powervs-workspace/ibm module to create PowerVS Workspace.
• Change name of DCs in Drop down for DAs
• Upgrade ibm provider to 1.58.1 for all DA soltuions
• Fullstack can now be consumed as a module. This module can deploy both variations of refrence architectures ( 3 VPCs or 1 VPC)
• Expose NFS disk configuration and now it is optional. Size and mount path of volume can be specified
• Faster parallel deployments of landing zone and Powervs infra
• fix: dns settings on landing zone vsi (upgraded to 1.1.4 version ansible collection ibm.power_linux_sap collection

Breaking Change :warning:

• Root module has been removed.
• :warning: Please backup the data on 10.20.10.4 private-vsi under the /nfs directory before upgrading to this.
• DAs will be affected with recreating the 1TB storage disk as the new landing zone version will recreate the disk in correct resource group. :warning: There will be down time :warning: if upgrading the fullstack stack solution. All the ansible roles will be triggered again, acl rules will be updated and the nfs disk will be back.
• When upgrading there will be downtime for about 20 mins, reboots of intel vsi will be made

Release required?

• [ ] No release
• [ ] Patch release (x.x.X)
• [ ] Minor release (x.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.

Merge actions for mergers

• When merging, use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author. The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).
• Merge by using "Squash and merge".

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[surajsbharadwaj]

/run pipeline

[terraform-ibm-modules-ops]

:tada: This PR is included in version 3.0.0 :tada:

The release is available on:

• GitHub release
• v3.0.0

Your semantic-release bot :package::rocket: