DocGen: changes to correctly merge metadata from tributaries #103
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.
This PR adds a few things to let update-mirror correctly merge services, SDKs, and validation metadata from tributaries. With upcoming update-mirror changes, this fully enables the feature that lets tributaries define their own services.yaml, sdks.yaml, and validation.yaml.
incremental=trueto DocGendefaultso it does loads the default metadata from itself but does not try to load any examples. This defines the "default" DocGen as containing all of the services, SDKs, and validation lists defined in this repo so that it can be used as a basis for merging in tributary examples and additional services, SDKs, and validation.DocGen.mergeto merge validation data fromother.With these changes, update-mirror can then:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.