-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More ibm -> linuxforhealth renaming #3855
Labels
enhancement
New feature or request
reindex
Resolution of issue will require a $reindex during upgrade
Comments
lmsurpre
added a commit
that referenced
this issue
Aug 9, 2022
and rename "ibm-x" index files to "generated-x" Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 9, 2022
and rename "ibm-x" index files to "generated-x" Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 9, 2022
Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 9, 2022
lmsurpre
added a commit
that referenced
this issue
Aug 9, 2022
and rename "ibm-x" index files to "generated-x" Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 9, 2022
Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 9, 2022
and rename "ibm-x" index files to "generated-x" Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 9, 2022
Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 9, 2022
and various other updates to avoid "ibm-" references in the code Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 9, 2022
1. ibm-internal-X-Compartment -> internal-X-Compartment 2. ibm_composite_X -> internal-composite-X And various other updates to avoid "ibm-" references in the code. Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 9, 2022
1. ibm-internal-X-Compartment -> internal-X-Compartment 2. ibm_composite_X -> internal-composite-X And various other updates to avoid "ibm-" references in the code. Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 9, 2022
1. ibm-internal-X-Compartment -> internal-X-Compartment 2. ibm_composite_X -> internal-composite_X And various other updates to avoid "ibm-" references in the code. Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 10, 2022
and the base URI that we use for our server-defined extended operations In both cases, http://ibm.com/fhir became http://fhir.linuxforhealth.org Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 10, 2022
The one place I left ibm.com URLs is the cql tests which have extensions from ibm.com/fhir/cdm ... those should be updated as well but not until that IG is available with a different base url Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 10, 2022
The one place I left ibm.com URLs is the cql tests which have extensions from ibm.com/fhir/cdm ... those should be updated as well but not until that IG is available with a different base url Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 10, 2022
The one place I left ibm.com URLs is the cql tests which have extensions from ibm.com/fhir/cdm ... those should be updated as well but not until that IG is available with a different base url Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 11, 2022
The one place I left ibm.com URLs is the cql tests which have extensions from ibm.com/fhir/cdm ... those should be updated as well but not until that IG is available with a different base url Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 11, 2022
The one place I left ibm.com URLs is the cql tests which have extensions from ibm.com/fhir/cdm ... those should be updated as well but not until that IG is available with a different base url Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 11, 2022
issue #3855 - remove the 'ibm' level from example paths
lmsurpre
added a commit
that referenced
this issue
Aug 11, 2022
issue #3855 - remove "ibm" from prefix for internal compartment params
lmsurpre
added a commit
that referenced
this issue
Aug 11, 2022
issue #3855 - replace ibm.com in all canonical uris
lmsurpre
added
the
reindex
Resolution of issue will require a $reindex during upgrade
label
Aug 15, 2022
lmsurpre
added a commit
that referenced
this issue
Aug 16, 2022
Signed-off-by: Lee Surprenant <lmsurpre@merative.com>
lmsurpre
added a commit
that referenced
this issue
Aug 17, 2022
issue #3855 - remove a few more ibm references
QA:
However, for item (3) in SearchExtensionsTest:
as this is just a unit test, there is no leak of this value in the product runtime. The test can be cleaned up at a convenient time in the future. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
reindex
Resolution of issue will require a $reindex during upgrade
Is your feature request related to a problem? Please describe.
There's a few more code-related locations that we should migrate before our 5.0
ibm-*
prefixes for internal search parametersibm.com
URIs in extension URLsDescribe the solution you'd like
No more references to IBM in code artifacts
Describe alternatives you've considered
Acceptance Criteria
References to 'ibm' from the codebase are reduced to a reasonable set. "reasonable" here is up for interpretation, but should not include ibm.com urls in data
Additional context
The text was updated successfully, but these errors were encountered: