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

Add HOW-TOs for common cloud-init use cases #758

Open
bpg opened this issue Nov 30, 2023 · 3 comments
Open

Add HOW-TOs for common cloud-init use cases #758

bpg opened this issue Nov 30, 2023 · 3 comments
Labels
acknowledged 📖 documentation Improvements or additions to documentation ✨ enhancement New feature or request

Comments

@bpg
Copy link
Owner

bpg commented Nov 30, 2023

Is your feature request related to a problem? Please describe.
There seems to be a lot of frustration around how cloud-init configuration is handled. We have multiple issues created in relation to various aspects of cloud-init functionality:

Describe the solution you'd like
Provide HOW-TOs with working examples and best practices to explain common cloud-init use cases.

Describe alternatives you've considered
None.

Additional context
None.

@bpg bpg added 📖 documentation Improvements or additions to documentation ✨ enhancement New feature or request labels Nov 30, 2023
@bpg-autobot
Copy link
Contributor

bpg-autobot bot commented May 29, 2024

Marking this issue as stale due to inactivity in the past 180 days. This helps us focus on the active issues. If this issue is reproducible with the latest version of the provider, please comment. If this issue receives no comments in the next 30 days it will automatically be closed. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@bpg-autobot bpg-autobot bot added the stale label May 29, 2024
@svengreb
Copy link
Contributor

Should not be stale…
I know the feeling of way too many open issues, but some bots often make it worse to manage projects and also have the risk of losing ideas and track of topics that are not really solved yet, but overlooked due to closed issues.

In my projects I heavily started to use discussions by converting open issues for topics that are not technical on the direct way. In the case of this issue I guess it is totally fine since it is a direct improvement and a kind of umbrella issue at the same time. Closing this issue might end up in more issues in the end because people (or you @bpg) would recreate them since no open issue exists. Or someone might also think that this topic is resolved.

Would it be possible to add new commands to the @bpg-autobot to convert an issue to a discussion instead, or tell it to ignore some issues like this one?

@bpg-autobot bpg-autobot bot removed the stale label May 30, 2024
@bpg
Copy link
Owner Author

bpg commented May 30, 2024

@svengreb good points!
Issues labeled with acknowledged will be ignored by the bot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledged 📖 documentation Improvements or additions to documentation ✨ enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants