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.

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

Use environment independent operator-sdk CLI version #2167

Closed
astefanutti opened this issue Mar 24, 2021 · 2 comments
Closed

Use environment independent operator-sdk CLI version #2167

astefanutti opened this issue Mar 24, 2021 · 2 comments
Labels
area/olm Related to the Operator Lifecycle Manager status/stale

Comments

@astefanutti
Copy link
Member

astefanutti commented Mar 24, 2021

The operator-sdk CLI binary is used for the generation of the OLM bundle. Currently it is expected to be present in the PATH, which leads to results that are environment dependent. As the operator-sdk CLI often introduces breaking changes, this leads to regressions and wasted cycles.

Similarly to what we did for controller-gen and kustomize CLI binaries, for which we use expected versions retrieved locally, the generation of the OLM bundle should rely on a fixed version of the operator-sdk CLI that's also retrieved locally.

@github-actions
Copy link
Contributor

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

@astefanutti
Copy link
Member Author

Fixed by @phantomjinx in #2284.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/olm Related to the Operator Lifecycle Manager status/stale
Projects
None yet
Development

No branches or pull requests

1 participant