docs: Clarify that max duration is required #5105
Open
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.
There is a discrepency between the UI and the docs over the Max Duration field in the UI. The UI says it is optional, but it appears it is required. This was documented incorrectly in the UI steps for creating an alias.
This PR corrects the incorrect step in the creating an alias procedure, and adds some additional text to the targets domain model and CLI topics to reinforce that the max duration is required and Boundary uses the default value if the user does not specify a value.
View the updates in the preview deployment:
session_max_seconds
definition)targets create
CLI doc > Usages by type (updatedsession_max_seconds
definition on SSH and TCP tabs)targets update
CLI doc > Usages by type (updatedsession_max_seconds
definition on SSH and TCP tabs)