Merge pull request #4 from EMCECS/OBSDEF-57542-Support-jammy-stemcell

YogeshSampalDell · web-flow · commit 84ecb74d3f36 · 2024-11-25T22:45:55.000+05:30
Release 2.3.3
diff --git a/README.md b/README.md
@@ -2,7 +2,7 @@
 
 ## Description
 
-This tile is created using the [Pivotal Tile Generator](https://docs.pivotal.io/tiledev/2-10/tile-generator.html) and deploys a service-broker application as a CF app. It deploys a sister project, the [ECS Service Broker](https://github.com/thecodeteam/ecs-cf-service-broker). For more instructions on using the broker once deployed, refer to the [Pivotal Network documentation](https://docs.pivotal.io/partners/ecs-service-broker/).
+This tile is created using the [Tile Generator](https://docs.vmware.com/en/VMware-Tanzu-Operations-Manager/3.0/tile-dev-guide/tile-generator.html) and deploys a service-broker application as a CF app. It deploys a sister project, the [ECS Service Broker](https://github.com/EMCECS/ecs-cf-service-broker/). For more instructions on using the broker once deployed, refer to the [ECS Service Broker documentation](https://emcecs.github.io/ecs-broker-tile/).
 
 This tile implements the following tile generator errands:
 
@@ -15,7 +15,9 @@ be configured from the PCF Ops Manager.
 
 ## Current Status
 
-Currently, the Tile version 2.3.2 is available for download via the [Pivotal Network product page](https://network.pivotal.io/products/ecs-service-broker/).
+Currently, the Tile version 2.3.3 is available for download via the [Broadcom Support portal](https://support.broadcom.com/group/ecx/productdownloads?subfamily=ECS%20Service%20Broker%20for%20VMware%20Tanzu).
+* ***This is the last release of the tile, no further versions will be released.***
+* ***Support for the tile will end on May 25, 2025. No support will be provided after this date.***
 
 ## Requirement
 
@@ -26,13 +28,13 @@ Currently, the Tile version 2.3.2 is available for download via the [Pivotal Net
 
 ## Build Tile
 * Clone the code to your local bosh machine
-* Install [Tile Generator Tool](http://docs.pivotal.io/tiledev/tile-generator.html)
+* Install [Tile Generator Tool](https://docs.vmware.com/en/VMware-Tanzu-Operations-Manager/3.0/tile-dev-guide/tile-generator.html)
 * Run command `tile build`
 
 ## Deployment
 * Using OpsManager website upload the tile
 * Add tile to dashboard
-* Configure tile [according to the documentation](https://docs.pivotal.io/partners/ecs-service-broker/index.html).
+* Configure tile [according to the documentation](https://emcecs.github.io/ecs-broker-tile/installing.html).
 * Apply Changes
 * Run cf service-brokers to check the broker status
 
@@ -69,7 +71,7 @@ Valid permissions include:
  * delete
  * none
 
-For more information about the ECS Broker usage please refer to [ECS CF service broker](https://github.com/emccode/final/ecs-cf-service-broker)
+For more information about the ECS Broker usage please refer to [ECS CF service broker](https://emcecs.github.io/ecs-broker-tile/usage.html)
 
 ### Testing
 
diff --git a/docs/index.md b/docs/index.md
@@ -30,25 +30,19 @@ With ECS Service Broker for VMware Tanzu, you can do the following:
 
 ## <a id="snapshot"></a>Product Snapshot
 
-| Element      | Details                                                                      |
-|:-------------|:-----------------------------------------------------------------------------|
-| Tile Version | 2.3.2                                                                        |
-| Release Date | February 23, 2024                                                            |
-| Software component version | 2.3.2                                                                        |
-| Compatible Ops Manager version(s) | v3.0.x, v2.10.x, v2.9.x                                    |
-| Compatible Tanzu Application Service version(s) | v4.0.x, v3.0.x, v2.13.x, v2.12.x, v2.11.x, v2.10.x, v2.9.x |
-| BOSH stemcell version | Ubuntu Xenial 621                                                            |
-| IaaS support | AWS, Azure, OpenStack, and vSphere                                           |
-| IPsec support? | No                                                                           |
+| Element      | Details                            |
+|:-------------|:-----------------------------------|
+| Tile Version | 2.3.3                              |
+| Release Date | November 25, 2024                  |
+| Software component version | 2.3.3                              |
+| Compatible Ops Manager version(s) | v3.0.x, v2.10.x            |
+| Compatible Tanzu Application Service version(s) | v6.0.x, v5.0.x, v4.0.x     |
+| BOSH stemcell version | Ubuntu Jammy 1.506                   |
+| IaaS support | AWS, Azure, OpenStack, and vSphere |
+| IPsec support? | No                                 |
 
 ## <a id="reqs"></a> Requirements
 
 ECS Service Broker for VMware Tanzu has the following requirements:
 
-+ [Tanzu Application Service](https://network.pivotal.io/products/elastic-runtime)
-
-
-## <a id="feedback"></a> Feedback
-
-Report bugs, make feature requests or ask questions on the [VMware Tanzu Feedback](mailto:pivotal-cf-feedback@pivotal.io) list,
-or send an email to [ECS Service Broker Support](mailto:ecs.open.service.broker@dell.com).
++ [Tanzu Application Service](https://support.broadcom.com/group/ecx/productdownloads?subfamily=VMware%20Tanzu%20Application%20Service%20for%20VMs)
diff --git a/docs/installing.md b/docs/installing.md
@@ -14,7 +14,7 @@ To install the service broker, you must configure the broker application to conn
 
 To start running the ECS broker, do the following:
 
-1. Download the product file from [Pivotal Network](https://network.pivotal.io/products/ecs-service-broker/).
+1. Download the product file from [Broadcom Support portal](https://support.broadcom.com/group/ecx/productdownloads?subfamily=ECS%20Service%20Broker%20for%20VMware%20Tanzu).
 
 1. Navigate to the Ops Manager Installation Dashboard and click **Import a Product** to upload the product file.
 
diff --git a/docs/release-notes.md b/docs/release-notes.md
@@ -1,5 +1,18 @@
 [Home](index.md) | [Installing](installing.md) | [Using](usage.md) | [Release Notes](release-notes.md) | [Troubleshooting](troubleshooting.md)
 
+## <a id="ver-2-3-3"></a> v2.3.3
+
+**Release Date:** November 25, 2024
+
+* ***This is the last release of the ECS Service Broker, no further versions will be released.***
+* ***Support for the broker will end on May 25, 2025. No support will be provided after this date.***
+
+In this release:
+
+* Support for Tanzu Application Services version 5.x and 6.x
+* Support for Ubuntu Jammy stemcell
+* Upgraded dependencies to address CVEs
+
 ## <a id="ver-2-3-2"></a> v2.3.2
 
 **Release Date:** February 23, 2024
diff --git a/docs/usage.md b/docs/usage.md
@@ -4,7 +4,7 @@ This topic describes how to use ECS Service Broker for VMware Tanzu after it has
 
 ## <a id='using'></a> Using ECS Service Broker for VMware Tanzu with an App
 
-To use ECS Service Broker for VMware Tanzu with an app, follow the procedures in this section to create a service instance and bind the service instance to your app. For more information about managing service instances, see [Managing Service Instances with the cf CLI](https://docs.pivotal.io/pivotalcf/devguide/services/managing-services.html).
+To use ECS Service Broker for VMware Tanzu with an app, follow the procedures in this section to create a service instance and bind the service instance to your app. For more information about managing service instances, see [Managing Service Instances with the cf CLI](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-platform-for-cloud-foundry/4-0/tpcf/services-managing-services.html).
 
 ### <a id="list"></a> View the Service
 
@@ -57,7 +57,7 @@ To enable your app to access the service instance, run `cf restage` or `cf resta
 
 After you bind your service instance to your app, you can find the credentials of your ECS S3 user in the environment variables of the app.
 
-Run `cf env APP-NAME` to display environment variables. The credentials are listed under the [VCAP_SERVICES](https://docs.pivotal.io/pivotalcf/devguide/deploy-apps/environment-variable.html#VCAP-SERVICES) key.
+Run `cf env APP-NAME` to display environment variables. The credentials are listed under the [VCAP_SERVICES](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-platform-for-cloud-foundry/6-0/tpcf/deploy-apps-environment-variable.html#VCAP_SERVICES) key.
 
 ```
 $ cf env sample-app
@@ -141,7 +141,7 @@ Run the `cf services` command to check the deletion status.
 ## <a id='using'></a> Use ECS Service Broker for VMware Tanzu with an App
 
 To use ECS Service Broker for VMware Tanzu with an app, follow the procedures in this section to create a service instance and bind the service instance to your app. For more information about managing service instances,
-see [Managing Service Instances with the cf CLI](https://docs.pivotal.io/pivotalcf/devguide/services/managing-services.html).
+see [Managing Service Instances with the cf CLI](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-platform-for-cloud-foundry/4-0/tpcf/services-managing-services.html).
 
 ### <a id="remote"></a> Connect an ECS Service to a Remote VMware Tanzu Instance
 
diff --git a/tile-history.yml b/tile-history.yml
@@ -15,4 +15,5 @@ history:
 - 2.2.1
 - 2.3.0
 - 2.3.1
-version: 2.3.2
+- 2.3.2
+version: 2.3.3
diff --git a/tile.yml b/tile.yml
@@ -138,11 +138,10 @@ packages:
 # strongly recommend you leave this alone so that your tile always
 # runs with the latest stemcell.
 #
-# stemcell_criteria:
-#   os: ubuntu-trusty
-#   requires_cpi: false
-#   version: '3062'
-
+#stemcell_criteria:
+#  os: ubuntu-jammy
+#  requires_cpi: false
+#  version: '1.506'
 # Add properties you want to pass to your applications.
 # Properties specified here will not be configurable by the user.
 #
