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.

Sign up for GitHub

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

Jump to bottom

Cloud init data source: Azure #355

Closed
mudler opened this issue Jun 30, 2021 · 2 comments
Closed

Cloud init data source: Azure #355

mudler opened this issue Jun 30, 2021 · 2 comments
Assignees
@davidcassany
Labels
kind/enhancement New feature or request
Projects
Releases

Comments

@mudler
Copy link
Contributor

mudler commented Jun 30, 2021

Is your feature request related to a problem? Please describe.
Our cloud-init support does not include data source from Azure. We are running a fork of linuxkit to have the data sources exposed separately, although we miss the Azure cloud-init support.

Describe the solution you'd like
Support for Azure in the cloud-init data sources

Describe alternatives you've considered

Additional context
See also linuxkit/linuxkit#3585 for an exampl
@mudler mudler added the kind/enhancement New feature or request label Jun 30, 2021
@mudler mudler self-assigned this Jun 30, 2021
@mudler mudler added this to ❆ Icebox in Releases Jun 30, 2021
@mudler mudler removed their assignment Jun 30, 2021
@mudler mudler moved this from ❆ Icebox to 💡 Untriaged in Releases Jul 6, 2021
@Itxaka Itxaka mentioned this issue Jul 14, 2021
Closed
5 tasks
@mudler
Copy link
Contributor Author

mudler commented Jul 14, 2021

See: mudler/yip#16 and https://github.com/davidcassany/linuxkit/pull/2

@mudler mudler moved this from 💡 Untriaged to 🏃🏼‍♂️ In Progress in Releases Jul 14, 2021
@davidcassany
Copy link
Contributor

Fixed by mudler/yip#16

Releases automation moved this from 🏃🏼‍♂️ In Progress to ✅ Done Jul 15, 2021
frelon pushed a commit to frelon/elemental-toolkit that referenced this issue May 12, 2023
Introduce ElementalError and exit codes (rancher#355)
bc06830 
* Introduce ElementalError and exit codes

 - ElementalError is an enhaced error interface that rbings along the
   exit code so we can exit properly from the main cmd command
 - Exit codes are stored along the error package
 - Build-disk command and related, but confined functions are all using
   the new ElementalError to propagate the exit code

Signed-off-by: Itxaka <igarcia@suse.com>

* Add comments to exit error constants

This should result in godoc automatically adding them to the
documentation visible on https://pkg.go.dev/

Signed-off-by: Itxaka <igarcia@suse.com>

* Rename files to sync with the rest of the repo

Signed-off-by: Itxaka <igarcia@suse.com>

* Add more info to exit codes for the docs

Signed-off-by: Itxaka <igarcia@suse.com>

* Maintain numerical order for ease of look

Signed-off-by: Itxaka <igarcia@suse.com>

* Generate the exit-codes md file automatically

This uses the go AST parser to parse the exit-codes.go file and extract
the exit value and the comment, and generate an md file with a nice
table with all the exit codes and its comment, where the comment is mean
to eexplain at a glance what the error came from (file open failed,
download failed, etc...) NOT a big explanation, that is what the logs
are for.

Also the list is ORDERED by error code, so no problems adding extra
codes in the future, the list will keep the order

Signed-off-by: Itxaka <igarcia@suse.com>

Signed-off-by: Itxaka <igarcia@suse.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@davidcassany davidcassany

Labels
kind/enhancement New feature or request
Projects
No open projects
Releases
✅ Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mudler @davidcassany