You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -97,6 +97,11 @@ The Bring Your Own Linux (BYOLinux) payload should be similar to the following:
97
97
}
98
98
```
99
99
100
+
> [!warning]
101
+
>
102
+
> In the example above, the `imageCheckSum` value has been obfuscated because it changes regularly whenever the target image is rebuilt.
103
+
>
104
+
100
105
Even though the configDrive user data could be sent to the API directly in clear text by escaping special characters, it is recommended to send a base64-encoded script to the API. You can use the following UNIX/Linux command to encode your data:
@@ -97,6 +97,11 @@ The Bring Your Own Linux (BYOLinux) payload should be similar to the following:
97
97
}
98
98
```
99
99
100
+
> [!warning]
101
+
>
102
+
> In the example above, the `imageCheckSum` value has been obfuscated because it changes regularly whenever the target image is rebuilt.
103
+
>
104
+
100
105
Even though the configDrive user data could be sent to the API directly in clear text by escaping special characters, it is recommended to send a base64-encoded script to the API. You can use the following UNIX/Linux command to encode your data:
@@ -97,6 +97,11 @@ The Bring Your Own Linux (BYOLinux) payload should be similar to the following:
97
97
}
98
98
```
99
99
100
+
> [!warning]
101
+
>
102
+
> In the example above, the `imageCheckSum` value has been obfuscated because it changes regularly whenever the target image is rebuilt.
103
+
>
104
+
100
105
Even though the configDrive user data could be sent to the API directly in clear text by escaping special characters, it is recommended to send a base64-encoded script to the API. You can use the following UNIX/Linux command to encode your data:
@@ -97,6 +97,11 @@ The Bring Your Own Linux (BYOLinux) payload should be similar to the following:
97
97
}
98
98
```
99
99
100
+
> [!warning]
101
+
>
102
+
> In the example above, the `imageCheckSum` value has been obfuscated because it changes regularly whenever the target image is rebuilt.
103
+
>
104
+
100
105
Even though the configDrive user data could be sent to the API directly in clear text by escaping special characters, it is recommended to send a base64-encoded script to the API. You can use the following UNIX/Linux command to encode your data:
@@ -97,6 +97,11 @@ The Bring Your Own Linux (BYOLinux) payload should be similar to the following:
97
97
}
98
98
```
99
99
100
+
> [!warning]
101
+
>
102
+
> In the example above, the `imageCheckSum` value has been obfuscated because it changes regularly whenever the target image is rebuilt.
103
+
>
104
+
100
105
Even though the configDrive user data could be sent to the API directly in clear text by escaping special characters, it is recommended to send a base64-encoded script to the API. You can use the following UNIX/Linux command to encode your data:
@@ -97,6 +97,11 @@ The Bring Your Own Linux (BYOLinux) payload should be similar to the following:
97
97
}
98
98
```
99
99
100
+
> [!warning]
101
+
>
102
+
> In the example above, the `imageCheckSum` value has been obfuscated because it changes regularly whenever the target image is rebuilt.
103
+
>
104
+
100
105
Even though the configDrive user data could be sent to the API directly in clear text by escaping special characters, it is recommended to send a base64-encoded script to the API. You can use the following UNIX/Linux command to encode your data:
@@ -97,6 +97,11 @@ The Bring Your Own Linux (BYOLinux) payload should be similar to the following:
97
97
}
98
98
```
99
99
100
+
> [!warning]
101
+
>
102
+
> In the example above, the `imageCheckSum` value has been obfuscated because it changes regularly whenever the target image is rebuilt.
103
+
>
104
+
100
105
Even though the configDrive user data could be sent to the API directly in clear text by escaping special characters, it is recommended to send a base64-encoded script to the API. You can use the following UNIX/Linux command to encode your data:
@@ -97,6 +97,11 @@ The Bring Your Own Linux (BYOLinux) payload should be similar to the following:
97
97
}
98
98
```
99
99
100
+
> [!warning]
101
+
>
102
+
> In the example above, the `imageCheckSum` value has been obfuscated because it changes regularly whenever the target image is rebuilt.
103
+
>
104
+
100
105
Even though the configDrive user data could be sent to the API directly in clear text by escaping special characters, it is recommended to send a base64-encoded script to the API. You can use the following UNIX/Linux command to encode your data:
@@ -97,6 +97,11 @@ The Bring Your Own Linux (BYOLinux) payload should be similar to the following:
97
97
}
98
98
```
99
99
100
+
> [!warning]
101
+
>
102
+
> In the example above, the `imageCheckSum` value has been obfuscated because it changes regularly whenever the target image is rebuilt.
103
+
>
104
+
100
105
Even though the configDrive user data could be sent to the API directly in clear text by escaping special characters, it is recommended to send a base64-encoded script to the API. You can use the following UNIX/Linux command to encode your data:
@@ -97,6 +97,11 @@ The Bring Your Own Linux (BYOLinux) payload should be similar to the following:
97
97
}
98
98
```
99
99
100
+
> [!warning]
101
+
>
102
+
> In the example above, the `imageCheckSum` value has been obfuscated because it changes regularly whenever the target image is rebuilt.
103
+
>
104
+
100
105
Even though the configDrive user data could be sent to the API directly in clear text by escaping special characters, it is recommended to send a base64-encoded script to the API. You can use the following UNIX/Linux command to encode your data:
0 commit comments