feat: include template ID in re-emitted boundary logs#21618
Merged
Conversation
Contributor
Documentation CheckUpdates Needed
Suggested addition:
This should be added after the Automated review via Coder Tasks |
Boundary policies are currently defined at the template level, so including the template ID in audit logs allows policy creators to filter and observe boundary activity for specific templates. This makes it easier to verify that policies are working as expected and to debug issues with specific template configurations.
89c92d6 to
1afa4af
Compare
Contributor
Documentation CheckPrevious Feedback✅ Addressed - The No Additional Changes NeededThe documentation update correctly documents the new Automated review via Coder Tasks |
evgeniy-scherbina
approved these changes
Jan 22, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Boundary policies are currently defined at the template level, so including the template ID in audit logs allows policy creators to filter and observe boundary activity for specific templates. This makes it easier to verify that policies are working as expected and to debug issues with specific template configurations.