Skip to content

fix(vscode): Fix azure connectors prompt silent fail on startup#9361

Open
andrew-eldridge wants to merge 2 commits into
mainfrom
aeldridge/azureConnectorWizardFix
Open

fix(vscode): Fix azure connectors prompt silent fail on startup#9361
andrew-eldridge wants to merge 2 commits into
mainfrom
aeldridge/azureConnectorWizardFix

Conversation

@andrew-eldridge

@andrew-eldridge andrew-eldridge commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Commit Type

  • feature - New functionality
  • fix - Bug fix
  • refactor - Code restructuring without behavior change
  • perf - Performance improvement
  • docs - Documentation update
  • test - Test-related changes
  • chore - Maintenance/tooling

Risk Level

  • Low - Minor changes, limited scope
  • Medium - Moderate changes, some user impact
  • High - Major changes, significant user/system impact

What & Why

When refreshing connection keys on startup, if azure connectors configuration doesn't exist in local settings then user is prompted with the azureConnectorWizard. This ultimately results in azureConnectorWizard silently failing after 'Use connectors from Azure' is selected since connection keys refresh is unawaited on startup. This is confusing to the user who then has to restart connectors setup when opening designer or running workflow.

As a solution, removed connections key refresh from startup entirely- it is now only done prior to starting runtime, so there is no longer an azureConnectorWizard prompt on startup.

Impact of Change

  • Users: Fixes connectors wizard silently failing on startup after selecting 'Use connectors from Azure'. User will now be prompted only when opening designer or running workflow instead
  • Developers: Refactored connectionKeys and other startup code, removed old tests
  • System: N/A

Test Plan

  • Unit tests added/updated
  • E2E tests added/updated
  • Manual testing completed
  • Tested in:

Contributors

@andrew-eldridge

@andrew-eldridge andrew-eldridge added the risk:low Low risk change with minimal impact label Jul 2, 2026
@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

PR Title

  • Current: fix(vscode): Fix azure connectors prompt silent fail on startup
  • Issue: None. The title is specific, actionable, and clearly describes the user-facing bug fix.
  • Recommendation: No change needed.

Commit Type

  • Properly selected (fix).
  • Only one commit type is selected, which matches the template requirements.

Risk Level

  • The selected risk level (Low) matches the diff scope and impact. The changes are localized and include refactoring plus startup behavior adjustment with test updates.
  • No mismatch found with the risk:low label.

What & Why

  • Current: Clear explanation of the startup race/silent failure and the rationale for moving connection key refresh out of startup.
  • Issue: None.
  • Recommendation: No change needed.

Impact of Change

  • The impact section is sufficiently clear and aligned with the code changes.
  • Recommendation:
    • Users: Good as written.
    • Developers: Good as written.
    • System: Good as written.

Test Plan

  • Unit tests are added/updated in the diff, which satisfies the test plan requirement.
  • Manual testing is also checked, but that is not required for pass/fail since unit tests are present.
  • No issue found.

Contributors

  • Contributors are listed (@andrew-eldridge).
  • No issue found.

⚠️ Screenshots/Videos

  • Not provided.
  • This is acceptable because the PR does not appear to be a visual/UI change requiring screenshots.

Summary Table

Section Status Recommendation
Title No change needed
Commit Type No change needed
Risk Level No change needed
What & Why No change needed
Impact of Change No change needed
Test Plan No change needed
Contributors No change needed
Screenshots/Videos ⚠️ Optional; not required for this non-visual change

Passed: the PR title and body are compliant, and the submitted risk level matches the label and observed scope.


Last updated: Thu, 02 Jul 2026 15:39:31 GMT

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR addresses a VS Code extension startup issue where the Azure connectors wizard could silently fail due to connection key refresh running (and not being awaited) during activation. It removes connection key refresh from extension startup and confines it to pre-runtime/debug flows, reducing unexpected prompts at activation time.

Changes:

  • Removed connection key refresh from extension activation and moved refresh to runtime/debug entry points.
  • Refactored parameterization-on-load prompt logic and renamed the command entrypoint to clarify intent.
  • Extracted the Logic App debug configuration provider into a shared utility and cleaned up related extension variables.

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
apps/vs-code-react/src/app/designer/appV2.tsx Switches codeful-workflow flag lookup to a local settings key string.
apps/vs-code-designer/src/main.ts Stops refreshing connection keys on activation; uses shared debug config provider and renamed parameterization entrypoint.
apps/vs-code-designer/src/extensionVariables.ts Removes unused ext.codefulEnabled flag.
apps/vs-code-designer/src/app/utils/startRuntimeApi.ts Refreshes connection keys immediately before starting the runtime API.
apps/vs-code-designer/src/app/utils/debug.ts Introduces logicAppDebugConfigProvider to centralize debug configuration resolution logic.
apps/vs-code-designer/src/app/utils/codeless/common.ts Uses non-null assertions for localSettings.Values when reading connector settings.
apps/vs-code-designer/src/app/utils/appSettings/localSettings.ts Ensures Values is initialized when parsing local.settings.json; minor type tightening.
apps/vs-code-designer/src/app/utils/appSettings/connectionKeys.ts Renames and narrows connection key logic to refreshConnectionKeys(projectPath) and updates telemetry naming.
apps/vs-code-designer/src/app/utils/appSettings/test/connectionKeys.test.ts Updates unit tests to the renamed/narrowed connection key refresh behavior and removes obsolete scenarios.
apps/vs-code-designer/src/app/commands/pickFuncProcess.ts Refreshes connection keys prior to debug attach/process selection flow.
apps/vs-code-designer/src/app/commands/parameterizeConnections.ts Renames startup parameterization entrypoint and refactors decision/prompt logic.
apps/vs-code-designer/src/app/commands/test/pickFuncProcess.test.ts Updates mocked connection key refresh function name and imports.

Comment on lines +37 to +40
const parameterizeConnectionsSetting = getGlobalSetting(parameterizeConnectionsInProjectLoadSetting);
if (parameterizeConnectionsSetting) {
return true;
}
Comment on lines +73 to +75
return undefined;
},
}
Comment on lines +12 to 16
* Refreshes the connection keys for the specified Logic App project, or all workspace projects by default.
* @param {IActionContext} context - The action context.
* @param {string} projectPath - The path to the Logic App project. If not provided, all Logic App projects in the workspace will be verified.
* @returns {Promise<void>} A promise that resolves when the verification is complete.
* @returns {Promise<void>} A promise that resolves when the refresh is complete.
*/
@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

📊 Coverage Check

The following changed files need attention:

⚠️ apps/vs-code-designer/src/app/commands/parameterizeConnections.ts - 60% covered (needs improvement)
⚠️ apps/vs-code-designer/src/app/utils/appSettings/localSettings.ts - 22% covered (needs improvement)
⚠️ apps/vs-code-designer/src/app/utils/debug.ts - 29% covered (needs improvement)

Please add tests for the uncovered files before merging.

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

Labels

pr-validated risk:low Low risk change with minimal impact

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants