Removes infrastructure-resources configuration#38088
Open
StefonSimmons wants to merge 2 commits into
Open
Conversation
…nfig.yaml and pull_config_preview.yaml
StefonSimmons
changed the title
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 does this PR do? What is the motivation?
removes
infrastructure-resourcesfrom the pull configs. we are now sourcing and processing this content viawebsites-sources(PR here).refactors
schematemplatemotivation: https://datadoghq.atlassian.net/jira/people/5fd13b2734847e0069ea3ec5/boards/18030?selectedIssue=WEB-7932
preview: https://docs-staging.datadoghq.com/stefon.simmons/no-cache-web-7932-infra-resources/infrastructure/resource_catalog/schema/
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Additional notes