-
Notifications
You must be signed in to change notification settings - Fork 23
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
Where can I find ansible-operator_darwin_amd64 for Mac #78
Comments
@venkataramanam: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
For local development users are told to run the ansible-operator locally but there are no macOS and Windows builds for users of those environments. fixes operator-framework#78
Type of question
General operator-related help
Question
What did you do?
There used to be an
ansible-operator
binary that could be run on a Mac till version https://github.com/operator-framework/operator-sdk/releases/tag/v1.31.0But I guess the refactoring of the
operator-framework
code moved the ansible operator to this repo: https://github.com/operator-framework/ansible-operator-pluginsNow I do not see any
ansible-operator
binary available for Mac (something likeansible-operator_darwin_amd64
)What did you expect to see?
It would be ideal if
ansible-operator
binary would be offered for Mac as well. This would really help test the operator outside of a container. We generally do that in development environment. Essentially runansible-operator run --watches-file ./watches.yaml
from a terminal on Mac for testing the dev changes.What did you see instead? Under which circumstances?
There is no
ansible-operator_darwin_amd64
binary for downloadEnvironment
Operator type:
/language ansible
Kubernetes cluster type:
OpenShift 4.15.9
$ operator-sdk version
$ go version
(if language is Go)$ kubectl version
Additional context
The text was updated successfully, but these errors were encountered: