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

Exec 'cpdb' should be executed after all updates? #31

Closed
cristifalcas opened this issue Jan 12, 2016 · 4 comments · Fixed by #139
Closed

Exec 'cpdb' should be executed after all updates? #31

cristifalcas opened this issue Jan 12, 2016 · 4 comments · Fixed by #139

Comments

@cristifalcas
Copy link
Contributor

I was wondering if the exec from postgresql module shouldn't be executed after any update of candlepin?

@ehelms
Copy link
Member

ehelms commented Jan 12, 2016

Update of the package? or update of configs? or really do you mean just everytime the module is applied?

@cristifalcas
Copy link
Contributor Author

package update

@ekohl
Copy link
Member

ekohl commented Aug 30, 2017

That might make sense. There's a different command to do the initial migrations than the migrate, but if the second is an exec that's refreshonly it could be ok. A migration should be noop if it's up to date but I'd like someone to confirm this.

@ekohl ekohl linked a pull request Apr 27, 2020 that will close this issue
@ekohl
Copy link
Member

ekohl commented Apr 27, 2020

Fixed in #139 / fadb503

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

Successfully merging a pull request may close this issue.

3 participants