Has anyone successfully uploaded files using AZ files step???
@Kostis can you help ?
Hello. Do you get an error message in the pipeline? Or an Azure related error?
Running plugin azure-files
Running freestyle step: main
(HTTP code 404) unexpected - pull access denied for codefresh/cf-azure-plugin, repository does not exist or may require ‘docker login’
[SYSTEM]
Message Failed to pull base image: codefresh/cf-azure-plugin:latest
Caused by Image Not Found Error
Documentation Link Freestyle · Codefresh | Docs
Exit code 44
Name NonZeroExitCodeError
[SYSTEM]
Message step: azure-files failed
Caused by plugin failed
Documentation Link Steps · Codefresh | Docs
Ah, this is a known issue. We recently updated the plugin library and some of them didn’t get set with the correct underlying docker image. It should be fixed this week.
Like I said, it should be fixed this week, but I built the image and made it available as a freestyle step if you want to get it working right away.
title: todaywasawesome-azure-files
image: todaywasawesome/azure-files
environment:
- 'ACCOUNT_NAME=${{ACCOUNT_NAME}}'
- 'ACCOUNT_KEY=${{ACCOUNT_KEY}}'
- 'SHARE_NAME=${{SHARE_NAME}}'
- 'PATH_TO_FILE=${{PATH_TO_FILE}}'
- 'DIRECTORY=${{DIRECTORY}}'
- 'ADD_TIMESTAMP=${{ADD_TIMESTAMP}}'
@todaywasawesome I am getting this
can I reach you via slack etc?
createShareUrl -> Share already created.
createDirectoryUrl -> https://cftestreports.file.core.windows.net/testreports/cypress Directory already created.
Looking for /codefresh/volume ...
events.js:177
throw er; // Unhandled 'error' event
^
Error: EISDIR: illegal operation on a directory, read
Emitted 'error' event at:
at internal/fs/streams.js:173:12
at FSReqCallback.wrapper [as oncomplete] (fs.js:461:5) {
errno: -21,
code: 'EISDIR',
syscall: 'read'
}
@Kostis , getting the error above… I have made sure that through the pipeline you can create a share and a directory so there is access to the az subscription.
@Kostis @todaywasawesome any updates on this ?
Hello. We will check. It will take some time however, because this issue requires an Azure test environment. Thank you for your patience.