@raharper, Your statement that this will be opt-in (disabled by default) does not reflect our intentions with this package. Upon review, my earlier statement was not as clear as I wish it was. In comment #31 I said:
> CPC (public cloud team) will continue with our baseline testing and for > releases earlier than focal where we will be pre-installing the package > in AWS images with the service disabled (opt-in) we will test that the > service is correctly disabled. The goal is to ship this in all supported Ubuntu images on AWS enabled by default for releases where it can be added prior to release. We would ship disabled (opt-in) for releases that are already supported in the field so as not to change behavior mid-release. So my statement regarding being disabled "for releases earlier than focal" reflects the goal of shipping enabled by default in Focal were this MIR accepted prior to Focal's release. I want to ensure this is reviewed with that intent in mind. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835114 Title: [MIR] ec2-instance-connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1835114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
