9127d81e03
See upstream changes: https://github.com/coreos/afterburn/pull/217 Signed-off-by: Robert Fairley <rfairley@redhat.com>
26 lines
1.1 KiB
Diff
26 lines
1.1 KiB
Diff
From 97e21b89edc80d52f2ddf0f34890752e0ab1c4b4 Mon Sep 17 00:00:00 2001
|
|
From: Jonathan Lebon <jonathan@jlebon.com>
|
|
Date: Fri, 17 May 2019 12:05:04 -0400
|
|
Subject: [PATCH] systemd: add comment to sshkeys@.service
|
|
|
|
This should help readers trying to piece together how SSH key
|
|
provisioning is wired up.
|
|
---
|
|
systemd/afterburn-sshkeys@.service.in | 4 ++++
|
|
1 file changed, 4 insertions(+)
|
|
|
|
diff --git a/systemd/afterburn-sshkeys@.service.in b/systemd/afterburn-sshkeys@.service.in
|
|
index f0677e0..f5a94d6 100644
|
|
--- a/systemd/afterburn-sshkeys@.service.in
|
|
+++ b/systemd/afterburn-sshkeys@.service.in
|
|
@@ -1,5 +1,9 @@
|
|
[Unit]
|
|
Description=Afterburn (SSH Keys)
|
|
+# Platforms which support SSH keys and provide a consistent source of metadata.
|
|
+# Platforms which support SSH keys but require selecting from multiple metadata
|
|
+# sources are not listed here; for those platforms, CT writes a drop-in which
|
|
+# adds the appropriate triggering condition and sets AFTERBURN_OPT_PROVIDER.
|
|
ConditionKernelCommandLine=|ignition.platform.id=aws
|
|
ConditionKernelCommandLine=|ignition.platform.id=azure
|
|
ConditionKernelCommandLine=|ignition.platform.id=digitalocean
|