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

Consistent register content during 'pack install' #3452

Merged
merged 4 commits into from
Jun 12, 2017

Conversation

arm4b
Copy link
Member

@arm4b arm4b commented Jun 7, 2017

Fixes #3445

The problem with the current approach is that st2ctl reload & st2 pack install & st2 pack register register different type of content by default, leading to confusion and error-prone scenarios when you got different functionality working for a pack, depending on situation.


With this PR we register all available content in pack by default during the st2 pack install.
This is already default behavior for st2 pack register, - follow that.

@arm4b arm4b requested review from Kami and enykeev June 7, 2017 16:11
@arm4b arm4b added the RFR label Jun 7, 2017
@arm4b arm4b force-pushed the fix/register-content-consistency branch from c069abe to a5aa6ed Compare June 9, 2017 14:31
@Kami
Copy link
Member

Kami commented Jun 12, 2017

Thanks.

I'm fine with that change - I originally left is so it only registered this content type because that's what happened in the past (pre-content management).

Let's please also add a changelog entry.

@arm4b arm4b added this to the 2.3.0 milestone Jun 12, 2017
@arm4b arm4b merged commit cd80e18 into master Jun 12, 2017
@arm4b arm4b deleted the fix/register-content-consistency branch June 12, 2017 15:20
@cognifloyd cognifloyd removed the RFR label Aug 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inconsistency in Pack register content
4 participants