-
Notifications
You must be signed in to change notification settings - Fork 33
Feat: helm for OHDSI webapi service #459
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
base: master
Are you sure you want to change the base?
Conversation
Please find the detailed integration test report here Please find the Github Action logs here |
Please find the detailed integration test report here Please find the Github Action logs here |
helm/ohdsi-webapi/templates/ohdsi-webapi-client-create-job.yaml
Outdated
Show resolved
Hide resolved
...according to cloud-automation version
... as well as auto creation of fence client entry.
7967a64 to
eb4aeaa
Compare
Please find the detailed integration test report here Please find the Github Action logs here |
Please find the detailed integration test report here Please find the Github Action logs here |
…g it ...and also ensure the secret exists before patching it
Please find the detailed integration test report here Please find the Github Action logs here |
helm/ohdsi-webapi/templates/ohdsi-webapi-client-create-job.yaml
Outdated
Show resolved
Hide resolved
Please find the detailed integration test report here Please find the Github Action logs here |
Please find the detailed integration test report here Please find the Github Action logs here |
…ientId and secret into webapi config
| } | ||
| http { | ||
| server { | ||
| listen 80; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
review?
Please find the detailed integration test report here Please find the Github Action logs here |
...and fix the $hostname issue in webapi config
| volumes: | ||
| - name: config-volume | ||
| secret: | ||
| secretName: "fence-config" # TODO does not seem to be used anywhere....instead "fence-dbcreds" is used... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clean-up?
| metadata: | ||
| name: ohdsi-webapi-config | ||
| type: Opaque | ||
| stringData: # TODO - should this be data (base64)?? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AidanHilt please advise
| # -- (bool) Will use ExternalSecret resources to pull secrets from Secrets Manager instead of creating them locally. Be cautious as this will override any fence secrets you have deployed. | ||
| deploy: false | ||
| # -- (string) Hostname for the deployment. | ||
| hostname: localhost |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe not a good default...?
| # -- (bool) Whether to automatically create a OIDC a client in Fence. | ||
| createFenceClientJobEnabled: true | ||
| # Service account for accessing webapi secrets and updating with OIDC client ID created in Fence (set to "default" if testing locally): | ||
| webapiSecretsServiceAccountName: "webapi-secrets" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AidanHilt where is the step that creates a service account with this "webapi-secrets" name? I think this is inherited from the previous kubernetes config, but not sure if these same service accounts are still present or if there should be a template adding the service account?
|
Failed to Prepare CI environment Please find the Github Action logs here |
Link to JIRA ticket if there is one: https://ctds-planx.atlassian.net/browse/VPODC-206
New Features