Skip to content
Snippets Groups Projects
Commit b95d6266 authored by Andy Schoenen's avatar Andy Schoenen :two:
Browse files

Change feature flag in JC OAuth setting controller

This changes the feature flag used to control the exposure of the
jira_connect_application_key setting. When GitLab.com is used as a
proxy for the GitLab.com for Jira Cloud app, it needs to fetch the
OAuth application ID from a self-managed instance.
jira_connect_oauth_self_managed_setting feature flag
will be enabled by default and rolled out to self-managed users.

This prepared self-managed users for the new feature and they will be
able to use it as soon as the jira_connect_oauth_self_managed
feature is enabled on GitLab.com
parent 0df4c998
No related branches found
No related tags found
1 merge request!104263Change feature flag in JiraConnect OAuth setting controller
......@@ -20,7 +20,7 @@ def show
def show_application_id?
return if Gitlab.com?
Feature.enabled?(:jira_connect_oauth_self_managed) && jira_connect_application_key.present?
Feature.enabled?(:jira_connect_oauth_self_managed_setting) && jira_connect_application_key.present?
end
def jira_connect_application_key
......
......@@ -38,9 +38,9 @@
end
end
context 'when jira_connect_oauth_self_managed disabled' do
context 'when jira_connect_oauth_self_managed_setting disabled' do
before do
stub_feature_flags(jira_connect_oauth_self_managed: false)
stub_feature_flags(jira_connect_oauth_self_managed_setting: false)
end
it 'renders not found' do
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment