Repository navigation
Migrate Financials beta cmdlet configuration and regenerate v3 module - #3899
Open
Ramses Sanchez-Hernandez (ramsessanchez) wants to merge 9 commits into
Open
Ramses Sanchez-Hernandez (ramsessanchez) wants to merge 9 commits into
Ramses Sanchez-Hernandez (ramsessanchez) wants to merge 9 commits into
Conversation
Record the empty shared directive ledger and compatible beta spec evidence without adding redundant overrides. Pin real beta operation identities and unaffected generator surfaces. Full beta generation remains a separate gate. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…z-financials-v3-migration
Use nine compatible shared variant groups with root defaults and retain alternative item-navigation writes through two exact path-based names. Update runtime beta API context, legacy/current lineage, empty shared-directive audit evidence and on/off regression coverage. Full beta build currently exposes the separate central Post/PostPath builder issue. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…z-financials-v3-migration
Honor the explicit user exclusion of the three exact /post action paths without suppressing collection POSTs or postAndSend. Keep specs and Kiota routes unchanged, preserve natural-ID groups and document this decision separately from the empty shared directive inventory. Regression coverage proves all 47 other POST routes remain generated with derived data on and off. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…ions Run the full queued beta Release pipeline on normal target 844672d with adapted Authentication 2.41.2 and isolated Kiota 1.36.1. Build succeeds with 713 compiled cmdlets; the Kiota client and original /post builders remain byte-identical to the prior diagnostic output. Preserve projects and generator locks together. New-source tree includes unmodified Kiota trailing whitespace. Runtime publication remains blocked by the separately tracked generic-header omission on PATCH 204 refetch (#3886); no blanket transport acceptance is claimed. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…z-financials-v3-migration
Preserve all shared natural-ID groups and the three user-approved terminal /post exclusions. Assert every supported beta PATCH emits only its mutation with no implicit GET or readback inputs; document actual 204 no-object and 200 typed-response behavior. Current module/configurator/naming/required-query and PATCH regression gates pass 450 tests on merged target 6475f3f. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Run full Kiota and wrapper beta Release generation on normally merged target 6475f3f after source correction 2cb7548. Preserve the client, all original client routes, locks and project boundary together; client and locks are byte-identical. Generated mutation cmdlets remove implicit GET and use the current generator's schema/query binding. Full pipeline reports OK with 713 compiled cmdlets; fresh no-incremental generator and module builds also succeed. The three exact terminal /post URI cmdlet exclusions, 47 other POST routes and existing natural-ID groups remain unchanged. No v1.0 generation or unmerged framework overlay. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Ramses Sanchez-Hernandez (ramsessanchez)
requested a review
from a team
as a code owner
November 6, 2026 01:55
This branch has not been deployed
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
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.
No linked issue; this implements the requested Financials v3 migration and beta generation.
Changes proposed in this pull request
src/Financials/Financials.md: it contains zero shared cmdlet directives, deferred parameter aliases/transforms, or deferred schema/response directives. Keep an honest emptymappingsledger with compatible-spec and legacy lineage evidence. Global and all profile-local readme directives are explicitly ignored and unchanged.FinancialCompanyItemCategoryByItemnoun because their alternative ItemId/ItemCategoryId sets have no shared minimal default. Apply the user's separate, explicit three terminal/postURI cmdlet exclusions, not a blanket POST exclusion or an invented legacy selection.powershell-v3at6475f3f5beb4908d39ea356db32bf1e0fd3273cb. Fresh generation, compilation, normal-manifest imports and authenticated offline transport gates pass after Remove automatic GET after successful PATCH #3886: PATCH 204 succeeds with no output and no GET; PATCH 200 returns its actual model in one PATCH. Callers explicitly invoke GET independently if desired; no new readback flag.Supported profile matrix
OKCompatible beta spec Git blob:
82f1d616cff0416dbd226e02268ebdde6fded7b1. Legacy beta lineage blob:0b7edf306b1217a3d6fd5c59c3e137bc7969fe28. Both OpenAPI inputs are unchanged.The complete user-excluded cmdlet operation set is:
All 47 other POST operations remain generated, including root/nested journal-line creation, customer creation, and sales-invoice
postAndSend,cancel, andsend. The 400 Kiota client files, including its lock and all three/postclient builders, are byte-identical to the prior client output. No input pruning, manual generated-source edits, #3881 copy, or global framework changes are included; #3881 remains open and deferred.Preserved commit boundaries
9e763b2b06e6179a14ad318f768925/postcmdlet exclusions3113a9d48edfa9a136352cb7548a9222da94b15fThe final corrective generation changes 410 cmdlet sources; existing client/project/lock output is genuinely unchanged. Full Git validation covers all 1118 changed paths, not a capped REST file list, and contains only Financials-owned source/generated output plus its dedicated test file. No bin/obj, binaries, packages, logs or evidence artifacts are committed.
Current validation commands and results
Session evidence root:
C:\Users\ramsess\.copilot\session-state\5d71a8fa-285b-4ef7-a70b-30621c1de9fb\files\post3886-6475-final.The full-build/TRX evidence above is unchanged. Current probe-only, actual
in-memory datastore guarded runtime/media evidence and canonical
handoff.jsonare in
C:\Users\ramsess\.copilot\session-state\5d71a8fa-285b-4ef7-a70b-30621c1de9fb\files\post3886-6475-memory-final.Both cloud proofs exercise all 27 exact natural-ID/ordinary route alternatives, the three absent cmdlet/retained client exclusions, all 47 retained compiled POST routes, escaped URLs, native optional queries and headers, real typed bodies/results, four PATCH 204 cases with one PATCH / zero objects / no GET while GET is configured to reject, four PATCH 200 cases with one PATCH / the actual typed model, and four independent caller-explicit GET successes and 403 errors. Ten WhatIf cases and ten genuine declined confirmations each send zero HTTP (one prompt per declined mutation); invalid binders fail before HTTP. Collection-create/action/GET/DELETE neighbors, beta cloud roots, unchanged factory BaseAddress, adapter reuse, context/reconnect/disconnect and explicit-token beta behavior pass. Financials has no native required-query operations; mandatory required-query transport cases are not applicable here.
Authentication is the normally packaged adapted 2.41.2 from the designated
4aa86cf9...\authentication-v2-sync\final-source\modulesroot. All 64 package-file hashes remain unchanged; physical nupkg SHA256 is2FC09BFE6B70D313BC56DF8ADCCFB1976FB4E90A1898BF8A916B4B8B792898EB. Isolated Kiota version is1.36.1+fd3bf87790149b87f40f7eae1a5feb9016625943, model parallelism 1. Wrapper output contains exactly its own three DLLs, no dependency preloads, and one correctly sourced Authentication-owned Kiota/RMS/URI/Multipart identity. No assembly injection, overlay, live Graph/OAuth, credential-store use, or Windows PowerShell 5.1 claim.Supplemental normal-manifest media controls use the existing customer-picture
/contentroute: PUT preserves exact octet-stream bytes and returns the actual typed Picture, while GET returns exact bytes or writes the exact OutFile without pipeline output. WhatIf and a genuine declined PUT confirmation each send zero HTTP (one prompt for the decline). Global and USGov beta URLs, generic headers, token pipeline, unchanged factory client and Authentication-owned dependency identities pass;media-beta-Global.jsonandmedia-beta-USGov.jsonretain the captures.Runtime isolation correction (probe only): normal Authentication import into
an additional confirmation runspace can reset the shared GraphSession datastore.
The corrected runtime/media probes finish all additional-runspace module
imports first, then reapply the existing normal
Set-MgTestDataStorehelperbefore the initial Connect. They assert the actual reflected shared
GraphSession.DataStore.GetType().FullNameisMicrosoft.Graph.Authentication.Test.Mocks.MockDataStorebefore Connect,transport, context/reconnect/disconnect/logout and cleanup. Every offline HTTP
capture independently enforces and records that actual type. Both Global and
USGov core/media reruns pass: 70 core checks plus 10 media checks per cloud,
160 actual datastore-boundary checks total. Source/helper hashes, boundaries,
actual types and captures are in the new runtime JSON and canonical handoff.
This does not infer actual credential I/O merely from an earlier datastore type.
The old raw runtime proofs/handoff stay unchanged as historical, not newly
guarded results. No source, Authentication package, build, TRX, generation,
commit, branch head or PR identity changed; the prior 713-export full build,
450-test result, all 400 client hashes and all 64 Authentication hashes remain
valid and are referenced by absolute path/hash in the new handoff.
Evidence and limits:
handoff.jsonretains scalar counters, full Git scope, exact input/source/Auth/tool/queue identities, command exits, normal manifest/assembly hashes and artifact SHA256s.compiled-beta-Global.jsonandcompiled-beta-USGov.jsoncontain actual request/body/header/response captures. Old 47-second compile failures, 844672 implicit-readback/header failures and isolated candidate results remain untouched as historical evidence, not relabeled passes. Current positive checks implement the user-approved no-readback contract. Offline tests do not certify live service validity or every API shape. No normalized beta-prefix/full raw-parity pass is claimed; the two documented ItemCategoryByItem write names and three explicit exclusions intentionally differ from frozen published metadata. Existing YamlReader NU1903 and Authentication managed-identity deprecation warnings remain outside this module scope.Other links