Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Turbo mode compatibility #24

Open
jobcespedes opened this issue Oct 3, 2021 · 2 comments
Open

Turbo mode compatibility #24

jobcespedes opened this issue Oct 3, 2021 · 2 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@jobcespedes
Copy link
Contributor

Bumping kubernetes.core version is being planned. It would be nice to make this collection compatible with turbo mode, available in the new version.
@jobcespedes jobcespedes mentioned this issue Oct 4, 2021
Closed
@asmacdo asmacdo added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Apr 18, 2022
@asmacdo asmacdo self-assigned this Apr 18, 2022
@asmacdo
Copy link
Member

asmacdo commented Apr 18, 2022

ping @gravesm

@gravesm
Copy link
Contributor

gravesm commented Apr 18, 2022

Here's the related PR for how we enable this in kubernetes.core collection: ansible-collections/kubernetes.core#169. All you really have to do is use the AnsibleTurboModule instead of the base AnsibleModule. We decided to use an env var to let the user control this import.

@asmacdo asmacdo removed their assignment Jan 24, 2023
@everettraven everettraven added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@asmacdo @gravesm @jobcespedes @everettraven