fix: fetch proxy only if jira is an enabled provider#2795
Merged
klesh merged 1 commit intoAug 23, 2022
Conversation
e2corporation
added
pr-type/bug-fix
3 tasks
e2corporation
force-pushed
the
jc-2789-restrict-jira-proxy-fetching
branch
from
6949130 to
79b573b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔁 Config-UI / Blueprints / Create Blueprint
This PR adds a needed restriction to the Create Blueprint Workflow so that JIRA Proxy API resources are only fetched if JIRA is an enabled Provider (ie. the user selects a JIRA connection for the current blueprint). In a scenario where JIRA is not detected, such as a blueprint with GitHub only -- API request calls for JIRA resources will not be made.
Does this close any open issues?
#2789