Constrained extension: DisableOutputBlobs feature implementation - #75
Merged
Conversation
alsanmsft
changed the title
Joseph Calev (jscalev)
requested changes
Jul 2, 2026
Bhaskar Brahma (D1v38om83r)
approved these changes
Jul 9, 2026
Joseph Calev (jscalev)
approved these changes
Jul 9, 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Overview:
This PR implements the ability to disable outputblobs as part of constrained extensions.
Problem:
As per the constrained extensions spec, one of the features of the run command policy is the ability to disable output blobs so that information does not leave the VM (at least, not because of the extension itself). Right now, if a customer provides an output blob URI or error blob URI, we automatically upload the output/error to that blob.
Solution:
If disableOutputBlobs is true, then we enforce that no outputblob URI or error blob URI has been passed in. When no URI is passed in, the extension already does not upload to any blob. We leverage this logic by enforcing that no URI is passed in.
This PR also includes unit tests validating the changes.