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

Go Operator Tutorial: plugins version issue #6778

Closed
hjeongb0320 opened this issue Jun 27, 2024 · 3 comments · Fixed by #6832
Closed

Go Operator Tutorial: plugins version issue #6778

hjeongb0320 opened this issue Jun 27, 2024 · 3 comments · Fixed by #6832
Labels
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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Milestone

Comments

@hjeongb0320
Copy link

Hi, recently, I'm following the quick start of operator sdk. In the process, I found that there was an error in the plugin-related docs in the middle, and I confirmed that it was fixed. However, there is the same part in the "tutorial" documentation, not the "quick-start" documentation (because the content itself is a process of re-installing and learning the principle from scratch), and that part was not modified. Recently, the correct issue was uploaded, and this seems to be a problem caused by confusion between quick start and tutorial, so I am reporting the issue.

[What needs to be revised]

  • before: Note If your local environment is Apple Silicon (darwin/arm64) use the go/v4-alpha plugin which provides support for this platform by adding to the init subCommand the flag --plugins=go/v4-alpha
  • after: Note If your local environment is Apple Silicon (darwin/arm64) use the "go/v4" plugin which provides support for this platform by adding to the init subCommand the flag --plugins="go/v4"

Thank you for your hard work, managers.

@acornett21
Copy link
Contributor

Hi @hjeongb0320 I'm not sure I understand this issue. go/v4 plugin has moved for the alpha phase to be GA, so the pull request that was merged is correct. If docs are incorrect, can you link to those pages in the issue?

@acornett21 acornett21 added kind/documentation Categorizes issue or PR as related to documentation. triage/needs-information Indicates an issue needs more information in order to work on it. labels Jul 1, 2024
@acornett21 acornett21 added this to the Backlog milestone Jul 1, 2024
@hjeongb0320
Copy link
Author

Hi, I mean in this docs, [Create a new project] !
https://sdk.operatorframework.io/docs/building-operators/golang/tutorial/

@acornett21 acornett21 added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. and removed triage/needs-information Indicates an issue needs more information in order to work on it. labels Jul 8, 2024
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants