Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use resource prefix when apiVersion is v1 (#371)
Use resource prefix when apiVersion is v1 SUMMARY When getting a resource from the core api group, the prefix was not passed, leading the lookup to happen in all api groups. This broad search is not really necessary and leads to problems in some corner cases, for example, when an api is deleted after the api group list is cached. This fix uses the 'api' prefix when the apiVersion is 'v1', as this is almost certainly what the user wants. As a fallback, to retain backwards compatibility, the old behavior is used if the first lookup failed to find a resource. Given that the module defaults to 'v1' for the apiVersion, there are likely many cases where a resource, such as StatefulSet, is used while failing to provide an apiVersion. While technically incorrect, this has worked in most cases, so we probably shouldn't break this behavior. Fixes #351 ISSUE TYPE Bugfix Pull Request COMPONENT NAME changelogs/fragments/364-use-resource-prefix.yaml plugins/module_utils/common.py
- Loading branch information