Comment 5 for bug 1869277
Revision history for this message
| Dan Watkins (oddbloke) wrote Re: [Bug 1869277] Re: write-ssh-key-fingerprints writes to console as 'ec2' | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
On Mon, Mar 30, 2020 at 03:50:25PM -0000, Scott Moser wrote:
> > Given that there is a better way available (and has been for long
> > enough that it should be available ~everywhere), would a more
> > appropriate path forward be to deprecate and/or remove this output,
> > instead of fixing it up?
>
> I'd say your two options are:
> a.) ignore the fact that this says 'ec2'. There are literally
> thousands of lines of output on a linux console. Don't fret over one of
> them listing a platform other than your own.
I think calling this "fret"ting is unfair. This is inconsistent
behaviour (nothing else in cloud-init logs as "ec2"), and it's
reasonable to wonder if something claiming to be "ec2" on the console
should be running on non-EC2 platforms.
> b.) drop it entirely.
>
> option 'c' would be to change it to say "azure" when it is on azure.
> That doesn't seem like it would help anyone, but only make it seem
> like someone should pay attention to it.
I think if we were to change it to anything, it would be to a
platform-agnostic "cloud-init" (which would also be consistent with the
rest of cloud-init's logging). The fact that this is "ec2" currently is
a historical artifact, not an intentional choice to use a platform name.