Skip to content
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

oc publish using version 0.34.8 to an S3 bucket ignoring the folder structure #386

Closed
ggehlot1980 opened this issue Feb 24, 2017 · 5 comments
Assignees

Comments

@ggehlot1980
Copy link

ggehlot1980 commented Feb 24, 2017

oc version - 0.34.8
os - Windows 10
I was trying to do an oc publish to an S3 bucket. My project gets published, but without any folder structure and all the file names are modified to include the folder names with backslash. So I get a flat structure for my project due to which the resources being referenced from my files becomes unavailable. This issue has been observed on MAC too.

@matteofigus
Copy link
Member

Thanks @ggehlot1980

I am trying to understand if this is a Windows 10 problem as I remember as similar issue a while ago: #30

If you see the same issue from a mac it may be unrelated. We use macs to publish components every day so the issue may be different. Either component related or registry related.

Just to be sure. When you say publish to an S3 bucket - you mean you are using the oc cli to publish and you are actually publishing to an OC registry right?

@ggehlot1980
Copy link
Author

ggehlot1980 commented Feb 24, 2017

Yeah I am using the oc cli to publish (oc publish package_name)and I am publishing to the oc registry only. My oc registry is already running locally on my windows machine on a given port and is linked to the the S3 bucket.

@matteofigus
Copy link
Member

Oh, I see, so the registry itself being running on Windows may actually be related to #30

@matteofigus
Copy link
Member

Ok, I confirm that running a registry instance in windows and publishing to it the S3 upload is broken.

screen shot 2017-02-24 at 16 33 55

When instead publishing from windows to a linux registry, I see an error: "package is not valid".

So, I believe the packaging phase that creates/unpackages the tar.gz file has more than one problem on windows machines.

@matteofigus
Copy link
Member

@ggehlot1980 this should be now fixed. Can you please retry by ensuring both Registry and CLI run with the latest version I just published: 0.35.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants