Removing WEBSITE_CONTAINER_READY=0 env variable check for DotnetIsolatedLinuxPlaceholder profile #2629
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.
In this PR, we added a profile condition to check if the environment variable
WEBSITE_CONTAINER_READY
is set to0
, following our wiki page. However, testing revealed this does not work, as the flex SKU did not set this environment variable. The Linux team conducted an initial investigation to find the impact of adding this environment variable to the container but found that other parts of the system expect this value to be not null rather than checking for a specific value (1). We have decided to remove this environment variable check, understanding the impact of this change.Pull request checklist
release_notes.md