Repository navigation
feat(web): share selected requests with customers behind a password - #4
Merged
Merged
Conversation
Add ADR 0003, mark ADR 0002 as extended, add the customer access check to the deploy guide and the new terms to CONTEXT.md. Refs: TEC-3584 Co-Authored-By: Claude Sonnet 5.5 <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
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.
What
A customer can open published documentation behind a generated password, seeing only the requests an
admin selected, for a limited time.
Decision record:
docs/adr/0003-customer-access-to-published-documentation.md, with the limits that were accepted.Changes to
template.ymlTTL attribute
ttlon the table anddynamodb:UpdateItemon the Lambda role.Manual CloudFormation test: PENDING. Do it before opening this pull request, then edit this line.
Deploy note
Publications saved before this change have no expiry, so they never expire.
How it was tested
bun run test:ci: 312 tests pass.bun run buildpasses.invalidates the old password, only the selected requests, no secrets on the page, editor sees it read-only.
Refs: TEC-3584