infra-azure-provisioning merge requestshttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/merge_requests2021-01-15T10:00:05Zhttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/merge_requests/134Parameterizing the integrationTestMavenGoal option in deploy-stages.yml2021-01-15T10:00:05Zharshit aggarwalParameterizing the integrationTestMavenGoal option in deploy-stages.ymlThis MR is makes changes to pass `integrationTestMavenGoal` as parameter from service pipelines
Services can opt to pass to a different goal to run Integration Tests. Default value is `package`
relates to https://community.opengroup.or...This MR is makes changes to pass `integrationTestMavenGoal` as parameter from service pipelines
Services can opt to pass to a different goal to run Integration Tests. Default value is `package`
relates to https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/72January - 21harshit aggarwalharshit aggarwalhttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/merge_requests/132Release/0.5.02021-01-06T23:10:23ZDaniel SchollRelease/0.5.0This MR satisfies the upgrades for Issue #75.
This MR satisfies the feature toggles for Issue #76This MR satisfies the upgrades for Issue #75.
This MR satisfies the feature toggles for Issue #76January - 21Daniel SchollDaniel Schollhttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/merge_requests/130Pipeline Cache Fixes2021-01-05T16:41:35ZJasonPipeline Cache Fixes## All Submissions:
-------------------------------------
* [**YES**/NO] Have you added an explanation of what your changes do and why you'd like us to include them?
* [**YES**/NO] I have updated the documentation accordingly.
* [**YES**...## All Submissions:
-------------------------------------
* [**YES**/NO] Have you added an explanation of what your changes do and why you'd like us to include them?
* [**YES**/NO] I have updated the documentation accordingly.
* [**YES**/NO/NA] My code follows the code style of this project.
## Current Behavior or Linked Issues
-------------------------------------
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
Relates to issue #73 and #74
- core code uses "install" maven goal. This puts the snapshot into the local repo, which is then cached. We only want to be caching the dependencies for a project, so we need to change the maven goal to "package" so that the built core code is not put in the local repository to be cached. **UPDATE: this has to be done so that the core code is in the local repo when the provider code is building. If it is not there, then the core code jar will be pulled from opengroup package repo. Therefore the goal should be kept as install.**
- there is no cache for the test code. This means the test core and azure test code dependencies are pulled down every time the pipeline runs
- there is not idea of a "version" in the current cache key. Adding in a version parameter allows for the potential to reset the cache either across all services by updating the "cacheVersion" parameter in this repo or reset the cache for a specific service by passing the parameter from the service pipeline .yml file. This is useful in case something accidently gets cached and we need to reset the cache (e.g, if core code accidently gets cached somehow)
## Does this introduce a breaking change?
-------------------------------------
- [YES/**NO**]
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
## Other information
-------------------------------------
<!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->
This code was tested with storage service in our dev ADO environment. The pipeline was ran twice to make sure that only dependencies were cached and that these cached dependencies were pulled correctly on the second run.January - 21JasonJasonhttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/merge_requests/123Adding New Storage Entitlement Test Data2021-01-24T16:46:33ZJasonAdding New Storage Entitlement Test Data## All Submissions:
-------------------------------------
* [**YES**/NO] Have you added an explanation of what your changes do and why you'd like us to include them?
* [**YES**/NO] I have updated the documentation accordingly.
* [**YES**...## All Submissions:
-------------------------------------
* [**YES**/NO] Have you added an explanation of what your changes do and why you'd like us to include them?
* [**YES**/NO] I have updated the documentation accordingly.
* [**YES**/NO/NA] My code follows the code style of this project.
## Current Behavior or Linked Issues
-------------------------------------
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
- storage service recently added a new test data requirement that the integration tester have the entitlement "data.integration.test". This MR adds that to our user_info_1 test data.
## Does this introduce a breaking change?
-------------------------------------
- [YES/**NO**]
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
## Other information
-------------------------------------
<!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->January - 21Daniel SchollDaniel Scholl