docs: add Boundary agent workloads research note - #69
Merged
Merged
Conversation
rkoster
requested review from
beyhan,
itsouvalas and
wayneeseguin
as code owners
September 22, 2026 07:42
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 is this note about?
This note researches HashiCorp Boundary as an identity-based access broker for agent workloads. It covers session-scoped target access, workers, credential brokering, lifecycle and audit considerations, and how Boundary might complement Cloud Foundry without replacing workload sandboxing.
Checklist
research/and uses a lowercase kebab-case filename.research/TEMPLATE.mdand has valid frontmatter (title,author,date,tags,status,sources).tags(see the suggested vocabulary inIDEATION.md).Test Plan
python3is unavailable; CI should run the repository's full checks.