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

Make independent mapping rules always enabled when APIAP is on #1133

Merged

Conversation

duduribeiro
Copy link
Contributor

@duduribeiro duduribeiro commented Aug 29, 2019

What this PR does / why we need it:

We need to make independent_mapping_rules always enabled for
services acting as product.

Which issue(s) this PR fixes

THREESCALE-3341

Depends on #1156

@duduribeiro duduribeiro self-assigned this Aug 29, 2019
@duduribeiro duduribeiro force-pushed the make_independent_mapping_rules_always_enabled_for_apiap branch from c588425 to 09fa0ef Compare August 29, 2019 16:19
app/models/service.rb Outdated Show resolved Hide resolved
Copy link

@makikata makikata left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As said in one of my comment no need to keep the rolling update as it will just be part of API as product. Nobody is using it anyway in SaaS.

@duduribeiro duduribeiro force-pushed the make_independent_mapping_rules_always_enabled_for_apiap branch 2 times, most recently from 7405cc6 to c7201fd Compare September 2, 2019 18:16
@Martouta Martouta changed the title Make independent mapping rules always enabled when APIAP is on [WIP] Make independent mapping rules always enabled when APIAP is on Sep 10, 2019
@Martouta Martouta added on hold Waiting for or blocked by something else. and removed on hold Waiting for or blocked by something else. labels Sep 10, 2019
@duduribeiro duduribeiro changed the title [WIP] Make independent mapping rules always enabled when APIAP is on Make independent mapping rules always enabled when APIAP is on Sep 11, 2019
@duduribeiro duduribeiro force-pushed the make_independent_mapping_rules_always_enabled_for_apiap branch from c7201fd to 9b18548 Compare September 11, 2019 20:23
Martouta
Martouta previously approved these changes Sep 12, 2019
Copy link
Contributor

@Martouta Martouta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍 But wait for 1 more review please 😉

@@ -44,7 +44,7 @@ def destroy
private

def authorize!
provider_can_use!(:independent_mapping_rules)
provider_can_use!(:api_as_product)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be provider_can_use!(:api_as_product) || provider_can_use!(:independent_mapping_rules) @thomasmaas ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say provider_can_use!(:api_as_product) is enough, unless we have customers on saas who are using this? As in our next on prem release all providers can and will use api_as_product

THREESCALE-3341

We need to make independent_mapping_rules always enabled for
services acting as product.
@duduribeiro duduribeiro force-pushed the make_independent_mapping_rules_always_enabled_for_apiap branch from 9b18548 to 2cb24b8 Compare September 12, 2019 16:55
Copy link
Contributor

@hallelujah hallelujah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK lets just leave the RU like that for now, and open the option to have it in SaaS (though not good UX)

@duduribeiro duduribeiro merged commit 21aee56 into master Sep 13, 2019
@duduribeiro duduribeiro deleted the make_independent_mapping_rules_always_enabled_for_apiap branch September 13, 2019 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
6 participants