Removes warning when dataset
is configured without setting service-name
#167
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.
Which problem is this PR solving?
As part of introducing Environments and Services, we also support users of Buildevents to configure the
service-name
associated to Build Events. However, for Build Events, the configurationdataset
is also still valid to allow users to name the bucket into which events from their pipelines and builds are sent to.We are removing the "Warning" prompting users to change their dataset config to be called service name.
Short description of the changes