Remove the need to specify api/ files, pull directly from the DCL #10199
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.
Fixes #8201
This PR removes the need to specify
api/
files for resources (although not samples quite yet) and pulls them directly off of the DCL's exported YAMLs. This means we'll stay up-to-date for better or for worse, although generally for the better. There's some pain in the upgrade- our YAMLs had drifted, and there were some dangerous-to-apply updates last I checked.Changes are contained to
main.go
, and all other changes in the PR are non-functional (removing api files, removing old overrides)Marked as WIP because of the drift- we need to resolve those to compatible before we can merge this. Outstanding issues:
config_membership
going required: Not believed to be a problem, as the field is effectively required alreadyconfigmanagement
/location
/feature
/membership
going required: Not believed to be a problem, same as forFeature
If this PR is for Terraform, I acknowledge that I have:
make test
andmake lint
to ensure it passes unit and linter tests.Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#5197