Apigee organization addons support #13654
Merged
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.
Resolves #13528. Added new resource (AddonsConfig) for Apigee which adds support for setting an organization's addons. This uses the setAddons Apigee API. Apigee organizations have service addons set by calling this API. One point of friction is that to retrieve current enabled addons, the GET organizations API must be used. Addons are returned in the addonsConfig property of the Organization structure. For all other verbs, the setAddons Apigee API is used. Below is a sample of the syntax proposed by this pull request, which aligns with the setAddons REST API.
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#7176