Open timcadman opened 6 months ago
This was found in PR #648 and applied a workaround adding dsMediation to the CI xenon whitelist
https://github.com/molgenis/molgenis-service-armadillo/blob/master/docker/ci/application.yml#L34
create_profile <- function(profile_name, key, auth_type) {
...
args <- list(
name = profile_name,
image = profile_default$container,
host = "localhost",
port = port,
packageWhitelist = return_list_without_empty(whitelist),
functionBlacklist = return_list_without_empty(blacklist),
options = list(datashield.seed = new_profile_seed)
)
then args
should reflect something similar as
"packageWhitelist": [
"my-whitelist-item"
],
"functionBlacklist": [
"my-blacklist-item"
],
"options": {
"datashield.privacyControlLevel": "permissive",
"datashield.seed": "898111733"
},
but is it called? No ... only through
create_profile_if_not_available(profile, profiles$available, token, auth_type)
We have added the wished for whitelist in
https://github.com/molgenis/molgenis-service-armadillo/blob/master/docker/ci/application.yml#L31-L36
but there is also the default settings when installing Armadillo
Expected that this would set packages to be whitelisted:
However CI failed because packages (e.g. dsMediation) not present. Workaround is to add package to docker/ci/application.yml