Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

pa CLI cannot reach default-prefixed environments (DNS ENOTFOUND); Dataverse connector rejects current as organization in default env

オープン
  • 何か問題がありますか？
#472 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
22/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
nodejs, powershell, typescript
領域
api, cli

調査の方向性

The payload names no file in this repository. The first failure is in the pa app init environment lookup in @microsoft/power-apps-cli 1.2.0, which builds the per-environment hostname without the default-environment prefix. Reproduce with pa app init -e <default-env-id> and compare the host it requests with the one that resolves. The second is the ListRecordsWithOrganization call with organization "current" in the Dataverse connector. Done means the default environment resolves and the connector accepts "current" or documents that it does not.

索引モデルが issue の本文から書いたものです。

説明

Issue 1: pa CLI network failures — wrong per-env hostname + IPv6

CLI: @microsoft/power-apps-cli 1.2.0 (global pa and npx --no-install power-apps, identical result), Node v24.18.1, Windows.

Repro (a) — wrong hostname for default env:

pa app init -n "my-app" -e c3df2a3c-e602-4ef6-b29d-3bac03b3991c

Fails after ~50ms:

Network request failed for GET https://c3df2a3ce6024ef6b29d3bac03b399.1c.environment.api.powerplatform.com/powerapps/environment?api-version=1&...
Details: getaddrinfo ENOTFOUND ... Non-existent domain

The correct host for this (default) environment carries the env prefix: defaultc3df2a3c...1c.environment.api.powerplatform.com (verified resolving, v4+v6). The CLI omits the prefix. Verified the constructed name is genuinely NXDOMAIN, not a local DNS issue. pa app init against a normal env in the same tenant works. (Worked around creation via deprecated pac code init, whose endpoints resolve correctly.)

Repro (b) — pa app push intermittently fails, IPv4 fixes it:

pa app push sometimes fails with network errors. Forcing IPv4 makes it reliable:

$env:NODE_OPTIONS="--dns-result-order=ipv4first"
pa app push   # consistently succeeds

DNS returns IPv6 (2603:1061:...) first for the API endpoints and the IPv6 path appears broken from this network — Node tries IPv6 first by default but the CLI surfaces a hard failure instead of falling back.

Expected: CLI resolves the environment endpoint (with prefix) before calling it, and either prefers IPv4 or retries across address families instead of hard-failing.

Issue 2: "current" as Dataverse connector organization fails only in default env

MicrosoftDataverseService.ListRecordsWithOrganization("current", "accounts", ...) fails at the connector runtime only in the default environment:

{"Message":"Invalid organization URL '' provided.","OperationId":"ListRecordsWithOrganization", ...}

Verified matrix (same call, same connector shared_commondataserviceforapps):

App Env "current" Full org URL
Solution-imported app normal env ok ok
Solution-imported app default env fails ok
Direct-created app (fresh portal connection, no solution involved) default env fails ok

Just a small observation from the default environment. The official connector reference documents the parameter only as Environment | organization | True | string | Choose an environment — no accepted value format, no "current" keyword anywhere. On my end I worked around it with plain ListRecords, which binds to the connection's own environment with no organization parameter.

Versions: @microsoft/power-apps 1.5.0, @microsoft/power-apps-cli 1.2.0, @microsoft/power-apps-vite 1.0.2.

主要言語
TypeScript
スター
513
フォーク
143
平均マージ
3日 9時間
マージ済み PR（30日）
12

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

microsoft/PowerAppsCodeApps のほかの issue

microsoft/PowerAppsCodeApps の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。