Uh oh!
There was an error while loading. Please reload this page.
[release/9.2] Remove AzureContainerAppEnvironmentResource BicepOutputReferences from public API - #8530
Merged
David Fowler (davidfowl) merged 1 commit intoApr 4, 2025
Conversation
…m public API These properties may change over time or be moved in the future. We don't want to expose them just yet. Will expose later if they need to be public. Contributes to #7811
Eric Erhardt (eerhardt)
requested review from
David Fowler (davidfowl) and Eric Erhardt (eerhardt)April 3, 2025 20:46
Dan Moseley (danmoseley)
approved these changes
Apr 3, 2025
David Fowler (davidfowl)
approved these changes
Apr 4, 2025
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport of #8529 to release/9.2
/cc Eric Erhardt (@eerhardt)
Customer Impact
This is public API we don't want exposed. It was pointed out in API review that we shouldn't be making this public yet. So removing the public API until we see a need to expose it.
Testing
Existing tests in the repo.
Risk
The only risk is if someone has been using a daily build and wants to use these properties, which is very unlikely.
Regression?
No.