Skip to content

Adding ansible operator workflow to the README #667

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

Merged

Conversation

shawn-hurley
Copy link
Member

Description of the change:
Adding workflow for the ansible operator in the README.

Motivation for the change:
Making the workflow just as obvious as golang

/cc @hasbro17

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 29, 2018
README.md Outdated
2. Define new resource APIs by adding Custom Resource Definitions(CRD) (This can be done in the new command)
3. Write the reconciling logic for your object using ansible playbooks and roles.
4. Define the mapping between the CRD definition in the `watches.yaml` file.
5. Use the SDK CLI to build and generate the operator deployment manifests
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Either keep or remove the period(full stop) at the end of the sentence for all bullet points.
4 has it. 5 doesn't.

Copy link
Contributor

@hasbro17 hasbro17 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM after nit

1. Create a new operator project using the SDK Command Line Interface(CLI)
2. Define new resource APIs by adding Custom Resource Definitions(CRD)
3. Define Controllers to watch and reconcile resources
4. Write the reconciling logic for your Controller using the SDK and controller-runtime APIs
5. Use the SDK CLI to build and generate the operator deployment manifests

The following workflow is for a new **Ansible** operator:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't steps 1, 2, 4 and 5 all largely happen as the result of the operator-sdk new command? I know it only gives you a single CRD to work with, but that will get most people a long way when they start. I'd describe the workflow more as:

  1. create new operator with the sdk
  2. write ansible to do stuff
  3. use sdk to build and run the operator
  4. optionally add additional CRDs for specific purposes

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree I am going to change better align with @mhrivnak's feedback

Copy link
Member

@joelanford joelanford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@lilic lilic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 lgtm

@shawn-hurley shawn-hurley merged commit c0f6021 into operator-framework:master Nov 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants