-
Post-migration efforts after move to FS1
We decided to move to FS1 with the least effort: toleration instead of exploitation of FS1. There are a couple of tasks required after the move was successfully completed: * Cleanup of obsolete services due to replacement by services hosted by FS1...0 Likely to implement
-
Ability to treat a field as an ID or key that we can use as an unique value
We ingest main content types for Events, Artists, and Venues and would like the ability to designate a specific ID (i.e. Event ID which is a text field within one of our content types) to act as a unique key. We have had issues with duplicate cont...0
-
FS1 Exploitation - Store Secrets in FS1 Vault instance
Once WCH has moved to FS1, the Vault instance can be used to store secrets (credentials, API Keys,...). See also https://github.ibm.com/dx/om-backlog/issues/2950 Likely to implement
-
Hide from Search Engines - Options for pages
Ability to set a flag on every landing page as to whether the page should be crawlable by search engines. Impact * remove the page from the sitemap that is generated* add a header in the SPA to indicate that it is not crawlable* SDK adjustment to ...0 Future consideration
-
Update Category Service to use a single datastore for all tenants.
Most WCH services currently store 1 tenant per Cloudant database this has resulted in WCH not following Cloudant best practices and resulted in a very high database count for the WCH solution. This puts the entire solution at risk as we grow our n...0
-
Add Cloudant Account support to WCH
At our expected rate of growth, we are pushing the boundaries of what a single Cloudant cluster can support. Our current database count is as 28,500 dbs in the WDC cloudant cluster and 13,500 dbs in the FRA Cloudant cluster. Adding 2,100 WCA tenan... -
Controlling Format of JSON API (e.g. GraphQL)
We want to be a headless CMS, but a lot of times clients need JSON in a specific format in order to be directly consumed. I think using GraphQL or having some mechanism to control the JSON format will be extremely valuable. Then we will be a headl...0 Likely to implement
-
Give a comprehensive overview of any NPM package that is used in WCH.
As https://www.npmjs.com/advisories/737 has shown, it can happen at any time that a package is identified to contain malicious code. If this package is used in production, we can find its usages quickly by checking the information gathered by the ...0
-
Enable our NPM repository to perform the NPM security audit.
Today, installing packages via npm also triggers a security audit scan while connected to the npmjs.com repository. Unfortunately, our own NPM repository does not support such audit requests nor does it forward them to npmjs.com. -
Retire published content
If we retire published content, please make sure that it is no longer accessible from the URL for distributing API information.0