CAPI v2 to v3 remediation work for - secureproxy-boshrelease

[ChrisMcGowan]

In order to continue to use this repo with Cloud Foundry after mid 2025, the CAPI v2 references in this repo need to be upgraded to support v3. Master Ticket: https://github.com/cloud-gov/private/issues/2287

CAPI Documentation Links for Reference

• Official TF Provider that supports v3
• Legacy CF-Community TF Provider to new CF Official V3 TF provider migration guide
• Official go-cflient support v3 - make sure to use version 3.0.0.alpha release or higher
• CF-Community CF Python Client - make sure to use version v1.38.2 or higher
• Official CAPI v3 API Reference - always use the latest version
• Official CAPI v2 to v3 upgrade guide - always use the latest version

Places to check/fix

Below are just SOME of the parts of this repo that need to be upgraded. This is NOT an all inclusive list and the assignee is responsible for flushing out all cases of CAPI v2 usage and migrating to v3:

• https://github.com/cloud-gov/secureproxy-boshrelease/blob/main/jobs/secureproxy/spec
• https://github.com/cloud-gov/secureproxy-boshrelease/blob/main/src/tic/t/tic.t

[ChrisMcGowan]

PR for link and read me cleanup - no v2 -> v2 work in the PR

[ChrisMcGowan]

There are 3 references in this code base for v2 :

• As an example in the job spec for an ignore path - not used in the codebase
• 2 settings in the tic unit test

CAPI has stated that even after the v2 shutdown they will keep /v2/info around. See: cloudfoundry/cloud_controller_ng#4280

In our deploy-cf we do now set both /v2/info and /v3/info to be ignored. Example

As far as updating the tic.t unit test - tic is not being actively used by CG nor any CG customers. There is no new deployment/testing of that portion of the code base and is a future candidate to be removed from this release so leaving that code base alone for now.