Skip to content

Issues: operator-framework/ansible-operator-plugins

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.

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

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

Ansible Operator proxy/cache not supporting set-based label selectors language/ansible Issue is related to an Ansible operator project
#99 opened Oct 2, 2024 by zeusng-fast
ansible-operator-plugins relying on abandoned python packages area/dependency Issues or PRs related to dependency changes
#86 opened Jul 26, 2024 by gaelgatelement
Add ansible watch config to run for every update type help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
#30 opened Aug 1, 2023 by jutley
Molecule scenarios not generated as documented help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation.
#32 opened Jul 4, 2023 by paterczm
Question: How to omit job events for Ansible operator? good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#19 opened Jun 1, 2023 by el-pako
ansible-operator: ignore existing resources at startup or conditional watches in watches.yaml triage/needs-information Indicates an issue needs more information in order to work on it.
#20 opened May 3, 2023 by jmazzitelli
Selector on watches.yaml not honoured lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. triage/support Indicates an issue that is a support question.
#31 opened Feb 14, 2023 by anupchandak
e2e-ansible-molecule test improvements lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
#21 opened Apr 26, 2022 by asmacdo
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.