Open eecavanna opened 2 weeks ago
- The "protocol" in the example occurrence above was
drs
and nothttps
. I don't know what types of clients use thatdrs
protocol. Would the correct "drop-in replacement" fordrs://drs.microbiomedata.org
be (a)drs://api.microbiomedata.org
or (b)https://api.microbiomedata.org
?
Hi @dwinston, during Thursday's infrastructure meeting, @shreddd and I talked about moving forward with getting rid of the drs.microbiomedata.org
subdomain. I am curious what you think about this "concern" I mentioned.
- Update Mongo documents to use...
Assuming there is nothing in the schema that says the current URL is valid (with respect to the schema) while the proposed URL is invalid (with respect to the schema), this update can be done live (e.g. via a changesheet or some other Runtime API endpoint) instead of via a migration.
Background
"DRS" stands for "Data Repository Service".
There is a DNS record (of type CNAME) for
drs.microbiomedata.org
defined on LBLnet (via IP Request). Since August 20, it has pointed to Cloudflare (previously, it pointed to Spin). There is a CNAME on Cloudflare that points to Spin. On Spin, there is a path on the productionapi
ingress that "listens" fordrs.microbiomedata.org
and routes it to the production Runtime.In practice, when I visit https://drs.microbiomedata.org, I am redirected to the Runtime (Swagger UI).
There is some documentation related to this subdomain, in the project README; here: https://github.com/microbiomedata/nmdc-runtime/?tab=readme-ov-file#data-exports
Conversations
A team member familiar with the subdomain wrote the following on Slack, in response to me asking whether there would be any harm in us deleting the aforementioned DNS records and ingress configuration:
I confirmed there is, indeed, at least one document in the database that has a field containing a URL that begins with
drs://drs.microbiomedata.org
(note thedrs
instead ofhttps
🤷 ). In this example, the name of the field isself_uri
and the document'sid
value is6m4e-1vbv-03
. You can find the document by issuing this query on the productionnmdc
database:Tasks
api.microbiomedata.org
instead ofdrs.microbiomedata.org
drs.microbiomedata.org
from the codebasedrs.microbiomedata.org
from documentationConcerns
drs
and nothttps
. I don't know what types of clients use thatdrs
protocol. Would the correct "drop-in replacement" fordrs://drs.microbiomedata.org
be (a)drs://api.microbiomedata.org
or (b)https://api.microbiomedata.org
?