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
Copy file name to clipboardExpand all lines: host/docs/Instance_workflow.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,8 @@ sequenceDiagram
61
61
1.`Operator` creates a valid ESP profile in `Provisioning Server 1`.
62
62
1. Assuming that it includes installing of a custom packages from the corresponding repository.
63
63
2.`Provisioning Server 1` returns a SHA256 checksum of an ESP profile to the `Operator`.
64
-
1. SHA256 checksum can be generated based on the specific repository's commit (e.g., example [here](https://stackoverflow.com/questions/61332371/how-to-get-a-sha256-hash-code-for-a-github-repo)).
64
+
1. SHA256 checksum can be generated based on the specific repository's commit (e.g., example
65
+
[how to get a sha256 hash code for a github repo](https://stackoverflow.com/questions/61332371/how-to-get-a-sha256-hash-code-for-a-github-repo)).
65
66
1. ESP profile installation artifacts must **NOT** affect SHA256 checksum, thus the checksum generation is
66
67
performed on the tarball file of the specific git commit.
67
68
2. In the case of multiple `Provisioning Servers`, where ESP profiles can be duplicated, we will ensure unique
0 commit comments