docs: rescue Phase 4 (compat + event-pipeline rename) and switch hash URL to GitHub Releases#457
Open
jagger wants to merge 3 commits into
Open
docs: rescue Phase 4 (compat + event-pipeline rename) and switch hash URL to GitHub Releases#457jagger wants to merge 3 commits into
jagger wants to merge 3 commits into
Conversation
…e folders to plural Phase 4 of the v0.62.0 documentation refresh. Compatibility: - Intro now states the module is tested through SS 12.0 (was vague "latest Secret Server release") - Add SS 12.0 notes subsection covering the response-filtering fixes shipped in v0.62.0 (Get-TssConfiguration, Get-TssRpcPasswordType, Get-TssDirectoryServiceSyncStatus, plus the general FilterTssResponse pass) Folder rename: - docs/commands/event-pipeline/ -> event-pipelines/ - docs/commands/event-pipeline-policy/ -> event-pipeline-policies/ - Plural matches sibling folders (secrets/, folders/, reports/, etc.) - Each moved page gets redirect_from: frontmatter pointing at its old URL, plus self-link in RELATED LINKS updated to the new path - Readme nav titles updated to plural - Add jekyll-redirect-from plugin to docs/_config.yml so the redirects actually render Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The cmdlet cast failures fixed in 0.62.0 are not specific to SS 12.0 — they show up whenever a deployed Secret Server returns response fields the module's typed C# classes don't yet model. That can happen across many SS releases as the API has grown. Update the compatibility page to describe the fixes generally (general FilterTssResponse pass plus three targeted nested-object fixes) rather than tagging them to SS 12.0. Also drop the "tested through SS 12.0" claim from the intro. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The previously-published hash URL on thyproservices.z20.web.core.windows.net no longer resolves (see #456). The v0.62.0 release already attaches Thycotic.SecretServer_hash.txt as a release asset, and the same pattern will be used going forward. Update install.md to link the v0.62.0 release asset directly and direct users at the Releases page for other versions. Closes #456 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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
PR #453 (Phase 4 of the v0.62.0 docs refresh) merged into the now-closed
jagger/docs-refresh-v0.62.0feature branch instead ofdev, so its content never landed on dev. This PR re-applies that work on top of current dev, plus fixes the dead hash URL flagged in #456.Re-landing from PR #453:
docs/getting_started/compatibility.md— reframed the 0.62.0 response-handling fixes (generalFilterTssResponsepass + three targeted nested-object cmdlets) as version-agnostic; the cast failures aren't SS 12.0-specificdocs/commands/event-pipeline/→event-pipelines/,event-pipeline-policy/→event-pipeline-policies/to match plural sibling folders (secrets/,folders/,reports/, etc.)redirect_from:frontmatter pointing at its old URL; self-links inside RELATED LINKS updated to the new pathjekyll-redirect-fromplugin todocs/_config.ymlso redirects actually renderNew — hash URL fix (#456):
https://thyproservices.z20.web.core.windows.net/Thycotic.SecretServer_hash.txtno longer resolves (DNS NXDOMAIN)Thycotic.SecretServer_hash.txtas a release asset; the same pattern is the recommended path going forwarddocs/getting_started/install.mdintegrity-verification snippet now points at the v0.62.0 release asset directly and tells users to grab the hash from the Releases page for other versionsCloses #456.
Verification
grep -rn "thyproservices" docs/ README.mdreturns no matches.Thycotic.SecretServer_hash.txtcontent matches the SHA256 of the CDN-distributed zip exactly:fbf3ab0ea1cf74b20a751b29e2526a9e7acef0a4b698864944a5715ce8b07b6bGenerated with Claude Code