Customizing and building a new version of an editable Global Package service in a target tenant

Ensure that these prerequisites are met:

  • An editable Global Package service is deployed to the target tenant through the Self-Service Portal.
  • Visual Studio Code and the BaaS extension are installed.
  • The service is displayed as editable (PE) in Deployed Services.

You can download the source files of an editable Global Package service, customize the service, and deploy a new version to the target tenant.

  1. In Visual Studio Code, connect to the target tenant by using the BaaS extension.
  2. In Deployed Services, locate the editable service delivered through the Global Package.
  3. Right-click the service and select Open Editable Service Package.
  4. Select a folder location and click Select Workspace Location.

    A workspace containing the complete service source code, manifest, and OpenAPI definitions is created.

  5. In Service Explorer, open the workspace for the downloaded service.
  6. Review the service files.

    Review these files and settings:

    • The current version in baas-manifest.json.
    • The service implementation files, including handlers, business logic, and configuration.
    • The OpenAPI definitions.

    The service follows the standard BaaS structure and can be modified in the same way as other BaaS services.

  7. Customize the service as required.

    You can make these types of changes:

    • Edit business logic in the handler implementations.
    • Add or modify OpenAPI definitions for endpoints.
    • Update configuration items in the manifest.
    • Adjust handler settings, such as timeouts and concurrency.
  8. Increment the service version in baas-manifest.json.

    For example, change the version from 1.0.0 to 1.0.1:

    {
						"version": "1.0.1"
						}

    Use the version number to distinguish the customized build from the version delivered by Infor.

  9. Press F1 and select BaaS: Build and Deploy.

    The service is built, packaged, and deployed to the target tenant. The customized version replaces the Global Package version as the active deployment.

  10. Verify the deployment.
    • In the ION API Gateway portal, verify that the service displays the updated version.
    • Test the customized endpoints.
    • Review the service logs in the BaaS portal to confirm that the service operates correctly.

The customized version of the editable Global Package service is deployed and active in the target tenant.