Problems installing (not publishing) collections #142
Replies: 3 comments 3 replies
-
|
I've tried using the same API key with a test script targeting the same artifactory instance and it's working from artifactory import ArtifactoryPath
art_api_key = "tokenHere"
art_url = "https://artifactory.megacorp.com/artifactory/corp-galactory-generic-local/corp-dev/"
galaxy_package = "corp_infra-collection_demo-2024.7.3.tar.gz"
galaxy_download = "test-download.tar.gz"
# API KEY
path = ArtifactoryPath(art_url + galaxy_package, apikey=art_api_key)
print(f'Downloading {galaxy_package} to {galaxy_download}...')
with path.open() as fd, open(galaxy_download, "wb") as out:
out.write(fd.read())
print(f'Done!')The package I pushed is in the same directory, just verifying I downloaded the same package |
Beta Was this translation helpful? Give feedback.
-
It should be making it there. Your output shows that it's not actually the download that's failing, it's the Your test script is accessing the download though, so it's not testing the same API call to artifactory. You may want to check if the token you're using with artifactory is authorized to list artifacts, it may be the case that it has limited permissions. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the quick reply-- Interesting! I will check on that with our Artifactory admins. In the meantime, it looks like my test script with the same token has access to + print(f'Testing stat on {art_url + galaxy_package}...')
+ print(path.stat())
print(f'Downloading {galaxy_package} to {galaxy_download}...')
with path.open() as fd, open(galaxy_download, "wb") as out:
out.write(fd.read())
print(f'Done!')I also gave setting I guess I can try wrapping my test script in |
Beta Was this translation helpful? Give feedback.
-
|
ok, that's very helpful! If that's the case then it doesn't appear that it's a permission problem with the token. Here's something interesting. Looking at the original stacktrace and the URL that failed, vs. the URL in your test script
I'm not entirely sure yet where the problem lies but it might be related? You could first try changing this line in your script: print(f'Testing stat on {art_url + galaxy_package}...')to this print(f'Testing stat on {str(path)}...')It still won't quite match, because the URL for stat is constructed inside another method: https://github.com/devopshq/artifactory/blob/master/artifactory.py#L862-L868 I suspect somewhere along the line paths are not being combined the same and that it might be resulting in a malformed path. Maybe setting a DEBUG log level on your test script will also help us see the URLs being used in internal calls? |
Beta Was this translation helpful? Give feedback.
-
|
Updated to include logging. Thanks again for keeping this conversation going! I checked with my Artifactory team, they believe my token's permissions are in order. new scriptimport logging
from artifactory import ArtifactoryPath
logging.basicConfig(level=logging.DEBUG)
logger = logging.getLogger(__name__)
art_api_key = "tokenHere"
art_access_token = ""
art_url = "https://artifactory.megacorp.com/artifactory/corp-galactory-generic-local/corp-dev"
galaxy_package = "corp_infra-collection_demo-2024.7.3.tar.gz"
galaxy_download = "test-download.tar.gz"
# API KEY
path = ArtifactoryPath(art_url + galaxy_package, apikey=art_api_key)
logger.info(f'Testing stat on {str(path)}...')
logger.info(path.stat())
logger.info(f'Downloading {galaxy_package} to {galaxy_download}...')
with path.open() as fd, open(galaxy_download, "wb") as out:
out.write(fd.read())
logger.info(f'Done!')resultrawwhat I extracted
|
Beta Was this translation helpful? Give feedback.
-
|
hm, I think at this point it might take running galactory locally on your machine so you can debug and step through it, I'm a bit stumped for the time being. |
Beta Was this translation helpful? Give feedback.
-
Hi again,
Galactory is doing a great job publishing collections to Artifactory. However I am receiving 403s from Artifactory & 500s from galactory when I try to install. I feel some authentication is not making it into the download request, but I'm not sure how to inspect that.
I've included debug-level working & not working log output below.
Config
Publishing - works as expected
galactory log
galactory log without token
Installing - not working as expected
Beta Was this translation helpful? Give feedback.
All reactions