Description of changes: to upgrade to node 20, the base image in buildconfig needs to be updated. the image in namex-fe-build was for node 16. I added a dockerfile (similar to the one from filings-ui). I updated https://console.apps.silver.devops.gov.bc.ca/k8s/ns/f2b77c-tools/buildconfigs/namex-fe-build/yaml
To deploy we no longer need to build namex-web (as the 2 build steps are merged in the Dockerfile).
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0), i.e sink for namex-fe-build is namex-front, which is used directly in deploymnetconfig.
Issue #:
Description of changes: to upgrade to node 20, the base image in buildconfig needs to be updated. the image in namex-fe-build was for node 16. I added a dockerfile (similar to the one from filings-ui). I updated https://console.apps.silver.devops.gov.bc.ca/k8s/ns/f2b77c-tools/buildconfigs/namex-fe-build/yaml To deploy we no longer need to build namex-web (as the 2 build steps are merged in the Dockerfile).
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0), i.e sink for namex-fe-build is namex-front, which is used directly in deploymnetconfig.
Looks like https://namex-dev.apps.silver.devops.gov.bc.ca/home is running fine.