WITSML Parser merge requestshttps://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests2023-09-01T15:38:28Zhttps://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/133Cherry-pick 'Feat/update aws python package version' into release/0.232023-09-01T15:38:28ZSrinivasan NarayananCherry-pick 'Feat/update aws python package version' into release/0.23**Original MR**: !132
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporati...**Original MR**: !132
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/pipelines/new?ref=cherry-pick-for-132)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/132Feat/update aws python package version2023-09-01T11:24:10ZBruce JinFeat/update aws python package version(AWS only changes)(AWS only changes)M20 - Release 0.23Bruce JinBruce Jinhttps://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/130Cherry-pick 'gc: fix render_dag_file.py' into release/0.222023-08-01T19:34:15ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'gc: fix render_dag_file.py' into release/0.22**Original MR**: !128
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporati...**Original MR**: !128
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/pipelines/new?ref=cherry-pick-for-128)M19 - Release 0.22David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/128gc: fix render_dag_file.py2023-08-01T15:45:54ZYan Sushchynski (EPAM)gc: fix render_dag_file.pyFix requests and limits for k8s pod operatorFix requests and limits for k8s pod operatorM19 - Release 0.22https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/126feat: User Context Ingestion2023-08-03T14:53:57ZDeepa Kumarifeat: User Context IngestionUpdated libraries and the clients to use useridUpdated libraries and the clients to use useridM20 - Release 0.23Deepa KumariDeepa Kumarihttps://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/125GONGR-7357-Refactor names in pipelines2023-06-27T10:55:49ZAndriy Halka [EPAM / GCP]GONGR-7357-Refactor names in pipelinesM19 - Release 0.22https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/124gc_move_to_airflow_2.62023-08-18T11:02:51ZYan Sushchynski (EPAM)gc_move_to_airflow_2.6M19 - Release 0.22https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/123GONRG-6690: Fix dag version2023-08-18T11:02:52ZYan Sushchynski (EPAM)GONRG-6690: Fix dag versionM19 - Release 0.22https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/122Cherry-pick 'Update cicd variables' into release/0.212023-05-22T21:48:03ZChad LeongCherry-pick 'Update cicd variables' into release/0.21**Original MR**: !121
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporati...**Original MR**: !121
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/pipelines/new?ref=cherry-pick-for-121)M18 - Release 0.21David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/121Update cicd variables2023-05-22T21:21:21ZAbhishek PatilUpdate cicd variablesUpdate cicd variablesUpdate cicd variablesM18 - Release 0.21Okoun-Ola Fabien HouetoAbhishek PatilOkoun-Ola Fabien Houetohttps://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/120fix: update aws build2023-05-19T18:55:03ZLong Chengfix: update aws buildM18 - Release 0.21Bill WangBill Wanghttps://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/119GONRG-7029: update anthos to baremetal2023-05-19T09:03:16ZYauheni Rykhter (EPAM)GONRG-7029: update anthos to baremetalM18 - Release 0.21Yauheni Rykhter (EPAM)Yauheni Rykhter (EPAM)https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/117Cherry-pick 'Merge branch 'master' of...' into release/0.202023-04-10T19:49:37ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Merge branch 'master' of...' into release/0.20**Original MR**: !116
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporati...**Original MR**: !116
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/pipelines/new?ref=cherry-pick-for-116)M17 - Release 0.20David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/116Merge branch 'master' of...2023-04-10T19:35:43Zetienne peyssonMerge branch 'master' of...Remains a unit test to make sure it worksRemains a unit test to make sure it worksM17 - Release 0.20etienne peyssonetienne peyssonhttps://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/115GONRG-6775: [FIX] Dataset DMS client returns deprecated retrieval instructions2023-03-31T09:57:11ZBohdan Solianyk [EPAM / GCP]bohdan_solianyk@epam.comGONRG-6775: [FIX] Dataset DMS client returns deprecated retrieval instructions# Description:
The MR is needed due to this changes: https://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/319
To fix this issue `get_retrieval_instructions` deprecated method was replaced with `retrieval_instru...# Description:
The MR is needed due to this changes: https://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/319
To fix this issue `get_retrieval_instructions` deprecated method was replaced with `retrieval_instructions`
# How to test:
# Changes include:
- [ ] Refactor (a non-breaking change that improves code maintainability).
- [x] Bugfix (a non-breaking change that solves an issue).
- [ ] New feature (a non-breaking change that adds functionality).
- [ ] Breaking change (a change that is not backward-compatible and/or changes current functionality).
# Changes in:
- [ ] GCP
- [ ] Azure
- [ ] AWS
- [ ] IBM
# Dev Checklist:
- [ ] Added Unit Tests, wherever applicable.
- [ ] Updated the Readme, if applicable.
- [ ] Existing Tests pass
- [ ] Verified functionality locally
- [ ] Self Reviewed my code for formatting and complex business logic.
# Other comments:
MR with [removing deprecated functions from DatasetDmsAPI](https://community.opengroup.org/osdu/platform/system/dataset/-/merge_requests/319)M17 - Release 0.20Bohdan Solianyk [EPAM / GCP]bohdan_solianyk@epam.comBohdan Solianyk [EPAM / GCP]bohdan_solianyk@epam.comhttps://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/114GONRG-6588: Manual job that deploy services to preship for release pipeline2023-08-18T11:02:54ZYurii Pelykh [EPAM / GCP]GONRG-6588: Manual job that deploy services to preship for release pipeline- `gc-deploy-dag:preship` job override defined- `gc-deploy-dag:preship` job override definedM17 - Release 0.20Yurii Pelykh [EPAM / GCP]Yurii Pelykh [EPAM / GCP]https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/113GONRG-6642: update release image for dag2023-08-18T11:02:56ZYauheni Rykhter (EPAM)GONRG-6642: update release image for dagM17 - Release 0.20Yauheni Rykhter (EPAM)Yauheni Rykhter (EPAM)https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/111Cherry-pick '[GC] Composer 2 support Autopilots' into release/0.192023-02-15T10:31:31ZSrinivasan NarayananCherry-pick '[GC] Composer 2 support Autopilots' into release/0.19**Original MR**: !109
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporati...**Original MR**: !109
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/pipelines/new?ref=cherry-pick-for-109)M16 - Release 0.19David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/110GONRG-6157: Refactor GC common pipeline file structure2023-08-18T11:02:57ZVolodymyr Pienskoi [EPAM / GCP]GONRG-6157: Refactor GC common pipeline file structureM17 - Release 0.20Volodymyr Pienskoi [EPAM / GCP]Volodymyr Pienskoi [EPAM / GCP]https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/merge_requests/109[GC] Composer 2 support Autopilots2023-02-14T17:45:42ZYan Sushchynski (EPAM)[GC] Composer 2 support AutopilotsGoogle Cloud fix.
Fix issue with k8s namespace in Composer2Google Cloud fix.
Fix issue with k8s namespace in Composer2M16 - Release 0.19Yauheni Rykhter (EPAM)Yauheni Rykhter (EPAM)