fix: disable observability on deploy if not explicitly defined in config #6776
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.
What this PR solves / how to test
Changes the deploy behavior deploys using the new versions API to disable observability if it isn't explicitly defined in the user's
wrangler.toml
. This behaves differently from howlogpush
andtail_consumers
work, where they must be explicitly removed, but we decided that this PR's behavior matches user expectations better.Fixes WO-186
Author has addressed the following