yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #78506
[Bug 1829441] [NEW] instance-data: surface merged cloud-config through cloud-init query command
Public bug reported:
It would be nice if cloud-init query could give simple cli access to the
on-disk merged cloud-config.
Use cases that this would help:
- customers wondering ultimately what default_user was used during cloud-init setup
- simple CLI to view what config modules are configured active on a given boot
- datasource configuration passed to cloud-init
- network configuration passed to cloud-init
We sometimes get questions in IRC for non-ubuntu distributions or
unofficial images where our response is to look in /etc/cloud/cloud.cfg
and cloud.cfg.d to see what modules/users are configured. it'd be fairly
simple to instrument this in the existing cloud-init query CLI.
** Affects: cloud-init
Importance: Undecided
Status: New
** Summary changed:
- instance-data: surface default user in instance-data.json
+ instance-data: surface merged cloud-config in instance-data.json
** Summary changed:
- instance-data: surface merged cloud-config in instance-data.json
+ instance-data: surface merged cloud-config through cloud-init query command
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1829441
Title:
instance-data: surface merged cloud-config through cloud-init query
command
Status in cloud-init:
New
Bug description:
It would be nice if cloud-init query could give simple cli access to
the on-disk merged cloud-config.
Use cases that this would help:
- customers wondering ultimately what default_user was used during cloud-init setup
- simple CLI to view what config modules are configured active on a given boot
- datasource configuration passed to cloud-init
- network configuration passed to cloud-init
We sometimes get questions in IRC for non-ubuntu distributions or
unofficial images where our response is to look in
/etc/cloud/cloud.cfg and cloud.cfg.d to see what modules/users are
configured. it'd be fairly simple to instrument this in the existing
cloud-init query CLI.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1829441/+subscriptions