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.

Sign up for GitHub

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

Jump to bottom

Gen3 Monthly Release 2022.12 va.data-commons.org 1671600721 #5497

Merged

m0nhawk merged 4 commits into master from chore/apply_202212_to_va_data-commons_org_1671600723

Dec 21, 2022

Contributor

PlanXCyborg commented Dec 21, 2022

Applying version 2022.12 to va.data-commons.org

PlanXCyborg added 2 commits

December 20, 2022 22:32


          apply version 2022.12 to va.data-commons.org

551aa77


          apply version 2022.12 to va.data-commons.org

e3688b0

PlanXCyborg requested review from nmetokishlubsky and a team as code owners

December 21, 2022 05:32


          feat(vadc): pin versions that should be pinned

be4c243

Contributor Author

PlanXCyborg commented Dec 21, 2022

va.data-commons.org/manifest.json

Deployment changes

awshelper
- Currently requires to manually update prisma api key in json format under this path in the adminvm (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
- ~/Gen3Secrets/prisma/apikey.json (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
- format has to be the following: (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
- { (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
- "AccessKeyID": "XXXX", (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
- "SecretKey": "XXXX" (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
- } (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
- This PR extends kube-setup-hatchery to create a kubernetes secret with for prisma cloud credentials, and extending the hatchery deployment to look for this secret and use it, if it exists. (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
metadata
- configuration files will need to be updated (PXP-8825 & BRH 206 metadata-service#65)

Breaking changes

arborist
- The GET /auth/mapping endpoint does not accept username as a query parameter anymore. It only supports parsing the username from the provided JWT. To specify a username, use the POST /auth/mapping endpoint. (PXP-10229 Client auth mapping arborist#153)
indexd
- Ensure you are using Fence>=2021.10. Remove deprecated GA4GH access endpoints. these have existed (and been used) from the Fence microservice since last year. See cloud automation change here (Revert "Revert "fix(migrate): improve acl->authz migration, remove de… indexd#338)
metadata
- The configuration file is not compatible with the previous release. This is due to the new support for defining a schema, new configuration options, and changes to the adapters. (PXP-8825 & BRH 206 metadata-service#65)


          feat: update Atlas/WebAPI to 2.12

3a805da

Contributor Author

PlanXCyborg commented Dec 21, 2022

va.data-commons.org/manifest.json

Deployment changes

awshelper
- Currently requires to manually update prisma api key in json format under this path in the adminvm (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
- ~/Gen3Secrets/prisma/apikey.json (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
- format has to be the following: (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
- { (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
- "AccessKeyID": "XXXX", (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
- "SecretKey": "XXXX" (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
- } (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
- This PR extends kube-setup-hatchery to create a kubernetes secret with for prisma cloud credentials, and extending the hatchery deployment to look for this secret and use it, if it exists. (BRH-301: Extend hatchery to launch prismacloud containers cloud-automation#2061)
metadata
- configuration files will need to be updated (PXP-8825 & BRH 206 metadata-service#65)

Breaking changes

arborist
- The GET /auth/mapping endpoint does not accept username as a query parameter anymore. It only supports parsing the username from the provided JWT. To specify a username, use the POST /auth/mapping endpoint. (PXP-10229 Client auth mapping arborist#153)
indexd
- Ensure you are using Fence>=2021.10. Remove deprecated GA4GH access endpoints. these have existed (and been used) from the Fence microservice since last year. See cloud automation change here (Revert "Revert "fix(migrate): improve acl->authz migration, remove de… indexd#338)
metadata
- The configuration file is not compatible with the previous release. This is due to the new support for defining a schema, new configuration options, and changes to the adapters. (PXP-8825 & BRH 206 metadata-service#65)

m0nhawk approved these changes

View reviewed changes

m0nhawk merged commit 0f99c83 into master

m0nhawk deleted the chore/apply_202212_to_va_data-commons_org_1671600723 branch

December 21, 2022 23:52

Contributor

m0nhawk commented Dec 23, 2022

This is part of VADC-310.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet