Closed markpearl closed 5 years ago
The storage account is aliased by a link:
{
"storage": {
"mystorageaccount": {
"account": "agcanrnaseqdiag",
"endpoint": "core.windows.net",
"account_key": "==",
"resource_group": "agcan-rnaseq"
}
}
}
mystorageaccount
is the alias you need to refer to, not agcanrnaseqdiag
. If you wish to refer to the storage account name, then change mystorageaccount
to whatever is appropriate.
@alfpark I'm actually using yaml files in the config directory.
Are you saying that the yaml file needs to look like the following?
storage: agcanrnaseqdiag: account: agcanrnaseqdiag account_key: == endpoint: core.windows.net resource_group: agcan-rnaseq
It depends on how you're referring to it in config.yaml
. If you are using agcanrnaseqdiag
, then yes, you'll need to modify the accompanying storage
config.
Closing, please re-open if you feel like the issue has not been resolved.
Hi Fred,
I'm currently running snakemake using Shipyard and I seem to be having permission issues. It's an Ubuntu 18.04 machine and I've gone by the example in github discussed here:
https://github.com/Azure/azure-hpc/tree/master/LifeSciences/SnakemakeBurst
As per my snakemake file, it seems to be having permission issues when trying to reference the inputs defined in the rules at the beginning of the file.
[image: image.png]
I feel as though it's a permission issue, but there's not other way to install snakemake in Ubuntu without "sudo apt-get install snakemake".
Do you have any suggestions for this? I'm really struggling with this.
I've attached my snakemake file and all azure-batch configs.
Would really appreciate your guidance on this.
-Mark
On Thu, Mar 7, 2019 at 10:21 AM Fred Park notifications@github.com wrote:
Closing, please re-open if you feel like the issue has not been resolved.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Azure/batch-shipyard/issues/263#issuecomment-470567707, or mute the thread https://github.com/notifications/unsubscribe-auth/AqWy_9PfeJAaGnORQzVTt_OYcBkDix6Jks5vUS5ogaJpZM4bblcv .
Problem Description
My credentials.yaml seems to be facing issues when trying to run the following shipyard command: SHIPYARD_CONFIGDIR=config ./shipyard pool add
After running the command, I receive the KeyError issues and the following stacktrace:
My yaml file seems correct when referencing it to the yaml template as per the batchyard installation. Any idea what could be causing this issue?