When the Helm chart is used to build and deploy a WildFly application on OpenShift, the link between the deployed application and its source is difficult to navigate (you have to look at various fields in the build-artefacts BuildConfig.
OpenShift has annotations that surfaces the source code location directly in its topology view:
app.openshift.io/vcs-uri- URI for the source code under version control
app.openshift.io/vcs-ref- Identifier for the version of the source code. Can be branch, tag or commit SHA for the application. If omitted master head of the default branch is assumed
These 2 annotations on the Deployment resource directly map to the Helm's build.uri and build.ref fields.
When the Helm chart is used to build and deploy a WildFly application on OpenShift, the link between the deployed application and its source is difficult to navigate (you have to look at various fields in the
build-artefactsBuildConfig.OpenShift has annotations that surfaces the source code location directly in its topology view:
app.openshift.io/vcs-uri- URI for the source code under version controlapp.openshift.io/vcs-ref- Identifier for the version of the source code. Can be branch, tag or commit SHA for the application. If omitted master head of the default branch is assumedThese 2 annotations on the
Deploymentresource directly map to the Helm'sbuild.uriandbuild.reffields.