Routing information is being placed in at develop time in the Angular api service files. This makes deployment involve app code changes. Here are the hardcoded values:

Background

This has been a challenge to address up to now in API backed Angular front-ends (architecture diagram) that are built using the s2i built approach (build diagram), which creates a high performance web server image but at the cost of extra build complexity.

Solution

Here is a simple pattern from Eagle EPIC that solves this in a few lines, meeting the https://12factor.net Factor III, "Store config in the environment" and allowing the app to be deployed based on settings alone. It handles the more complicated s2i builds (other projects that expose environment settings in a similar pattern like MDS use a much simpler build process).

Please see the following areas of code:

1. Here's where the Angular app consumes the settings from the server and replaces the hardcoded routes
2. Make sure this line gets placed in the HTML head as it needs to run prior to app load
3. Create the landing point for the environment variables at server build time
4. When the pod starts up, and on every subsequent redeployment, set the variables. Javascript was chosen over JSON as it's a direct plugin for the existing variables in api.ts without having to do overhead to handle the JSON. MDS uses JSON.
5. Pass the environment variables along
6. Settings exposed in OpenShift

You can check if your settings are exposed by (if you used the same pattern as above) visiting https://your-front-end-url/publicServerEnvironmentSettings.js

And remember to set your app to redeploy on environment variable change. That way your app will get new environment settings without needing a build.

Cheers!

PS. If you have a discrete admin site, the above solution uses the same pattern with slight variations on the path (/admin in the server build and image startup script but html stays the same). Note the use of uniquely named client-side variables to avoid collisions (public vs admin).

• Site: https://www-mem-mmt-dev.pathfinder.gov.bc.ca
  New Alerts
  • Modern Web Application [10109] total: 5:
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/sitemap.xml
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/scripts.eacbff647151c627f6ea.bundle.js
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/polyfills.b6c070aba42d4edf1cd2.bundle.js
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/robots.txt
  • Cookie Without SameSite Attribute [10054] total: 2:
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/robots.txt
  • Information Disclosure - Suspicious Comments [10027] total: 3:
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/main.15ec5ff16065cfc3cfa0.bundle.js
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/scripts.eacbff647151c627f6ea.bundle.js
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/polyfills.b6c070aba42d4edf1cd2.bundle.js
  • CSP Scanner: Wildcard Directive [10055] total: 3:
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/robots.txt
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/sitemap.xml
  • Cross-Domain JavaScript Source File Inclusion [10017] total: 3:
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/sitemap.xml
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/robots.txt
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/
  • Incomplete or No Cache-control and Pragma HTTP Header Set [10015] total: 4:
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/robots.txt
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/sitemap.xml
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/styles.4f73c19f0aa0b987f0f7.bundle.css
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/
  • Timestamp Disclosure - Unix [10096] total: 7:
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/main.15ec5ff16065cfc3cfa0.bundle.js
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/main.15ec5ff16065cfc3cfa0.bundle.js
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/main.15ec5ff16065cfc3cfa0.bundle.js
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/main.15ec5ff16065cfc3cfa0.bundle.js
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/polyfills.b6c070aba42d4edf1cd2.bundle.js
    • ..
  • CSP Scanner: script-src unsafe-inline [10055] total: 3:
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/robots.txt
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/sitemap.xml
  • CSP Scanner: style-src unsafe-inline [10055] total: 3:
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/robots.txt
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/sitemap.xml
    • https://www-mem-mmt-dev.pathfinder.gov.bc.ca/

View the following link to download the report.
RunnerID:122991053

This issue is a kind reminder that your repository has been inactive for 181 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

• If this product is being actively maintained, please close this issue.
• If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

TL;DR

Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).

Why Topic

In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means its critical that we work to make our content as discoverable as possible; Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.

What to do

Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic.

That's in, you're done!!!

How to use

Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.

Pro Tip 🤓

• If your org is not in the list below, or the table contains errors, please create an issue here.

• While you're doing this, add additional topics that would help someone searching for "something". These can be the language used javascript or R; something like opendata or data for data only repos; or any other key words that are useful.

• Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.

• If your application is live, add the production URL.

Ministry Short Codes

NOTE See an error or omission? Please create an issue here to get it remedied.

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)