Investigating
Bind Cloud Manager Maven Build Pipelines to known and documented IP Ranges
| Request for Feature Enhancement (RFE) Summary: | Our Corporate Nexus Infrastructure (which contains non-public artifacts needed for the Build Pipeline) has IP restrictions in place. We have to explicitely IP-whitelist any client that tries to fetch artifacts from it. Currently, the Build Pipeline cannot access it because the IPs used are non-deterministic and not documented. |
| Use-case: | Maven Build Pipelines need artifacts from Corporate Nexus that has IP restrictions in place. |
| Current/Experienced Behavior: | Maven Build Pipelines are not allowed to access Corporate Nexus. |
| Improved/Expected Behavior: | The IP addresses used by the Maven Build Pipelines are documented, hence whitelisted at our infrastructure, the Maven Build Pipelines can access the Corporate Nexus and fetch the required artifacts. |
| Environment Details (AEM version/service pack, any other specifics if applicable): | AEM as a Cloud Service |
| Customer-name/Organization name: | Helvetia Versicherungen |
| Screenshot (if applicable): | |
| Code package (if applicable): |