entitlements-azure merge requestshttps://community.opengroup.org/osdu/platform/security-and-compliance/entitlements-azure/-/merge_requests2021-08-18T12:47:40Zhttps://community.opengroup.org/osdu/platform/security-and-compliance/entitlements-azure/-/merge_requests/43Add node selector2021-08-18T12:47:40ZDzmitry_Paulouski (slb)Add node selectorUpdate devops/azure/chart/templates/deployment.yaml, devops/azure/chart/values.yaml, devops/azure/chart/helm-config.yaml filesUpdate devops/azure/chart/templates/deployment.yaml, devops/azure/chart/values.yaml, devops/azure/chart/helm-config.yaml fileshttps://community.opengroup.org/osdu/platform/security-and-compliance/entitlements-azure/-/merge_requests/42Master2021-08-05T09:41:59ZDzmitry_Paulouski (slb)Masterhttps://community.opengroup.org/osdu/platform/security-and-compliance/entitlements-azure/-/merge_requests/39Add node selector2021-08-05T09:43:29ZDzmitry_Paulouski (slb)Add node selector## All Submissions:
-------------------------------------
* [YES] Have you followed our code review [guidelines](https://github.com/microsoft/code-with-engineering-playbook/blob/master/pull-requests/code-reviews/readme.md)?
* [YES] Have ...## All Submissions:
-------------------------------------
* [YES] Have you followed our code review [guidelines](https://github.com/microsoft/code-with-engineering-playbook/blob/master/pull-requests/code-reviews/readme.md)?
* [YES] Have you added an explanation of what your changes do and why you'd like us to include them?
* [NO] I have updated the documentation accordingly.
* [NA] I have added tests to cover my changes.
* [YES] All new and existing tests passed.
* [YES] My code follows the code style of this project.
* [YES] I ran lint checks locally prior to submission.
## What is the current behavior?
-------------------------------------
Currently, we have only one node pool for services and system workloads.
## What is the new behavior?
-------------------------------------
We are going to move workloads to a new node pool with enabled autoscaling. Here you can find the details:
[Issue link](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/167)
## Does this introduce a breaking change?
-------------------------------------
- [NO]
This change has a strong dependency on the following MR and should be merged **only** after it:
https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/merge_requests/324https://community.opengroup.org/osdu/platform/security-and-compliance/entitlements-azure/-/merge_requests/32upgrade libs2020-12-10T00:23:11ZMingyang Zhuupgrade libsupgrade libs to resolve the high and critical vulnerabilities reported by white sourceupgrade libs to resolve the high and critical vulnerabilities reported by white sourceMingyang ZhuMingyang Zhuhttps://community.opengroup.org/osdu/platform/security-and-compliance/entitlements-azure/-/merge_requests/31upgrade libs2020-12-08T18:28:06ZMingyang Zhuupgrade libsUpgrade libs to resolve high and critical vulnerabilities reported by white sourceUpgrade libs to resolve high and critical vulnerabilities reported by white sourceMingyang ZhuMingyang Zhuhttps://community.opengroup.org/osdu/platform/security-and-compliance/entitlements-azure/-/merge_requests/28Restoring No-access user from cosmos DB after completing integration testing2020-11-10T19:27:12ZDuvelis CaraoRestoring No-access user from cosmos DB after completing integration testingThere are some test cases where the no-access user is updated/deleted from the data cosmos DB.
The no-access user is used from other services during the integration testing, so if the no-access user is not present in cosmos DB other ser...There are some test cases where the no-access user is updated/deleted from the data cosmos DB.
The no-access user is used from other services during the integration testing, so if the no-access user is not present in cosmos DB other service integration testing will fail.Duvelis CaraoDuvelis Caraohttps://community.opengroup.org/osdu/platform/security-and-compliance/entitlements-azure/-/merge_requests/25Fix for enabling root level SP2020-12-25T05:24:03Zharshit aggarwalFix for enabling root level SP
This PR contains fix for enabling support for Root Level SP [ Note: This is only an interim solution ]
We are adding a check in getGroups method that if a call is made from a certain SP [aka Root SP] we will return all the groups in th...
This PR contains fix for enabling support for Root Level SP [ Note: This is only an interim solution ]
We are adding a check in getGroups method that if a call is made from a certain SP [aka Root SP] we will return all the groups in the tenant by querying TenantInfo collection
For the check we are comparing object ID's [OID] of the service principals. The OID of the Root SP will be read from the key vault.
Appropriate infra changes done through following Pull Requests [PR1 ](https://github.com/Azure/osdu-infrastructure/pull/182), [PR2](https://github.com/Azure/osdu-infrastructure/pull/183) and [PR3](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/merge_requests/8), though it might take some time for changes to get deployedhttps://community.opengroup.org/osdu/platform/security-and-compliance/entitlements-azure/-/merge_requests/18Draft: Resolve "Disabling AAD Authentication from R2 Services"2020-09-11T12:14:03ZKiran VeerapaneniDraft: Resolve "Disabling AAD Authentication from R2 Services"Closes #1Closes #1