[StealthTalk] Fix publisherId in SolutionMetadata.json to match Partner Center registered publisher#14463
Merged
v-atulyadav merged 1 commit intoJun 15, 2026
Conversation
…alkinc' to match Partner Center registered publisher ID The publisherId in SolutionMetadata.json was set to a brand-name shorthand 'stealthtalk' instead of the actual Partner Center registered publisher ID 'stealthtalkinc'. This caused Partner Center certification check 300.4.1.1 to fail: the Marketplace identifier publisherId.offerId derived from the GitHub source did not match the 'Offer Name' in Partner Center. Changes: - SolutionMetadata.json: publisherId 'stealthtalk' -> 'stealthtalkinc' - Package/mainTemplate.json: surgical update of solutionId variable to embed corrected publisherId (no V3 rebuild, to keep the diff minimal and avoid V3-tool cosmetic field reordering) - Package/3.0.0.zip: repacked with the patched mainTemplate.json
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Aligns the StealthTalk solution’s marketplace identifier with the Partner Center–registered publisher by updating the publisherId, and propagating that change into the packaged template/zip.
Changes:
- Update
Solutions/StealthTalk/SolutionMetadata.jsonpublisherIdfromstealthtalktostealthtalkinc. - Update packaged
solutionIdinPackage/mainTemplate.jsonto reflect the newpublisherId. - Rebuild
Package/3.0.0.zipto match the updated packaged artifacts.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| Solutions/StealthTalk/SolutionMetadata.json | Corrects publisherId to match the Partner Center publisher identifier. |
| Solutions/StealthTalk/Package/mainTemplate.json | Updates solutionId to keep packaged content aligned with the corrected publisher ID. |
Contributor
Author
|
Friendly heads-up @v-atulyadav — small one-line metadata fix to address Partner Center Best Practice Test 300.4.1.1. There are 2 Copilot review comments that I have responded to with context inline; Would appreciate a quick review when convenient. Thanks! |
v-atulyadav
approved these changes
Jun 15, 2026
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.
Summary
Follow-up to the merged StealthTalk Anomalous Authentication solution (PR #14259). This PR corrects a single metadata value in
SolutionMetadata.json:The original value was a brand-name shorthand; the corrected value matches the actual Partner Center registered publisher ID. This resolves Partner Center Best Practice Test 300.4.1.1 ("Offer Name in Partner Center must match SolutionMetadata.json"), which was failing because the Marketplace identifier derived from the GitHub source (
stealthtalk.stealthtalk-sentinel-solution) did not match the Partner Center "Offer Name" (stealthtalkinc.stealthtalk-sentinel-solution).No functional changes; no analytic rule, hunting query, parser, workbook, or playbook content modified.
Change(s)
Solutions/StealthTalk/SolutionMetadata.json—publisherIdcorrected from"stealthtalk"to"stealthtalkinc".Solutions/StealthTalk/Package/mainTemplate.json— surgical update of the solutionId variable to embed the corrected publisherId. No V3 rebuild was performed to keep the diff minimal and avoid the V3 packaging tool's cosmetic field-reordering noise. The substantive change is one line.Solutions/StealthTalk/Package/3.0.0.zip— rebuilt so the bundled artefacts match the source.Reason for Change(s)
SolutionMetadata.json". The original PR (New Solution: StealthTalk Anomalous Authentication v3.0.0 #14259) used a brand-name shorthandstealthtalkaspublisherId, which did not match the actual registered Partner Center publisher IDstealthtalkinc. The Marketplace identifierpublisherId.offerIdderived from the source must equal the Partner Center "Offer Name" — this PR aligns the two values.Version Updated
Solution_StealthTalk.json,mainTemplate.jsonvariables (_solutionVersion), and the zip filename (3.0.0.zip). This is also the version currently in flight in Partner Center, so no source-vs-Partner Center version mismatch is introduced.Testing Completed
arm-ttkvalidation: 51 / 51 pass.Solutions/StealthTalk/: clean.Package/3.0.0.zipcontents extracted and scanned: ASCII-only, all artefacts matchmainTemplate.jsonsource.Package/mainTemplate.jsonand the unpackedPackage/3.0.0.zipcontain the correctedstealthtalkincvalue in all embedded publisher metadata locations; no stalestealthtalkstandalone publisher value remains._solutionVersionconfirmed at3.0.0end-to-end (Solution_StealthTalk.json,mainTemplate.json, zip filename).Checked that the validations are passing and have addressed any issues that are present
References