@tjaalton and @ahasenack: I was mistaken in not reporting back to this
original bug. In talking with PMs over a year ago, we agreed the
potential risk of breakage and additional requirements for image
creation didn't warrant making this change. Unless a compelling customer
requires common top-level keys for all supported series, cloud-init
user-data can support per-series behavior with jinja templates like the
following cloud-config user-data:
## template: jinja
#cloud-config
{% if distro_version in ["16.04", "18.04" -%}
ubuntu_advantage:
{% else -%}
ubuntu_pro:
{% endif -%}
token: YOUR_TOKEN
So a workaround exists for customers where automation/scripts may want to
provide a single user-data file which supports both Ubuntu ESM and LTS releases.
Let's close this as rejected.
** Changed in: cloud-init (Ubuntu Xenial)
Status: Incomplete => Won't Fix
** Changed in: cloud-init (Ubuntu Bionic)
Status: Incomplete => Won't Fix
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067660
Title:
deprecate ubuntu_advantage config key from user-data in favor of
ubuntu_pro
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2067660/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
