-
Notifications
You must be signed in to change notification settings - Fork 898
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
add prod dirs via .gitkeep #21355
add prod dirs via .gitkeep #21355
Conversation
Checked commit kbrock@2b26458 with ruby 2.6.3, rubocop 1.13.0, haml-lint 0.35.0, and yamllint |
Is there an associated issue on the rpm build side to stop creating these directories? Also, is there any source code that tries to do like a |
created associated PR that no longer WIP: verify the rpm properly creates these directories |
|
YAY -- good find. we are creating them up front but that is a great example of a directory that should be removed |
Actually that one didn't exist on my appliance and the UI worker was trying to create it when I hit the application settings page. (sorry if you were talking about going to be creating them up front) |
Yea, this PR should create those directories with the |
I wanted to delete https://github.com/ManageIq/manageiq/blob/master/app/models/git_repository.rb#L226 But was getting failed builds that didn't seem totally logical. ref1 ref2 Either way, leaving the |
these 3 directories need to be in production (and writeable) They were created by our rpm build process, but moving that here to keep it in one place. This is following suit for what we are doing to create the log directory
unwip: the dirs show up with correct permissions after an rpm upgrade. |
part of #20394
the flip side in the rpm is: ManageIQ/manageiq-rpm_build#174
These 3 directories need to be in production (and writeable)
They were created by our rpm build process, but moving the here
to keep the logic in a place that is accessible by both pods and appliances.