This repo provides an example customizing the public IBM VSI on VPC landing zone deployable architecture by enforcing a set of values and providing a json override file for modifying the deployment architecture pattern with out the need to modify the actual code.
In addition, this repo provides:
- A module that extends the custom infrastrucutre with a VSI running an apache server
- A blueprint that will provision both the custom infrastructure and the apache Module as a single blueprint
- Create a custom deployable architecture and deploy it as a custom tile to the IBM cloud catalog.
- Create a custom module that extends the custom deployable architecture (based on the IBM VSI module) to deploy an Apache server.
- Create a blueprint deploys both the custom module and custom deployable architecture's base infrastructure and an apache server on top of it
- create a pipeline that will publish the custom architecture and apache server as private solutions on the IBM public catalog.
Catalog tiles:
- custom-deployable-arch is a generic deployable architecture for the network landscape.
- custom-apache is a deployable architecture as a workload which runs a secure apache server.
The Apache tile will hold both a terraform and a blueprint. The blueprint is used to deploy both the app infra and the base deployable architecture. The terraform template is use in the case that you want the apache server to run on an existing Secure Infra deployment.
Publish Pipeline
Included in this example is a Github Action to illustrated automated publishing to an IBM catalog. The supplied action makes the following assumptions as pre-requisites.
- a secret in the repo has been configured for a IBM Cloud api key for an account that has sufficient IAM permissions to provision resources.
- the Action imports, validates, publishes new versions as they are created when a git release is created. It is assumed that the offerings have already been created in the target catalog which is done only once.