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: README.md
+23-4Lines changed: 23 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,6 +60,7 @@ This command will upload the repo in tarball to S3.
60
60
It will auto-detect if the tarball is for maven or npm
61
61
62
62
* For maven type, it will:
63
+
63
64
* Scan the tarball for all paths and collect them all.
64
65
* Check the existence in S3 for all those paths.
65
66
* Filter out the paths in tarball based on:
@@ -70,10 +71,8 @@ It will auto-detect if the tarball is for maven or npm
70
71
* Upload these artifacts to S3 with metadata of the product.
71
72
* If the artifacts already exists in S3, update the metadata
72
73
of the product by appending the new product.
73
-
74
74
* NPM type (TBH): We need to know the exact tarball structure
75
75
of npm repo
76
-
77
76
* For both types, after uploading the files, regenerate/refresh
78
77
the index files for these paths.
79
78
@@ -107,10 +106,30 @@ This command will refresh the index.html for the specified path.
107
106
108
107
* Note that if the path is a NPM metadata path which contains package.json, this refreshment will not work because this type of folder will display the package.json instead of the index.html in http request.
109
108
110
-
### charon-validate: validate the checksum of files in specified path in a maven repository
109
+
### charon-cf-check: check the invalidation status of the specified invalidation id for AWS CloudFront
This command will validate the checksum of the specified path for the maven repository. It will calculate the sha1 checksum of all artifact files in the specified path and compare with the companied .sha1 files of the artifacts, then record all mismatched artifacts in the report file. If some artifact files misses the companied .sha1 files, they will also be recorded.
128
+
129
+
### charon-checksum-refresh: refresh the checksum files for the artifacts in the specified maven repository
This command will refresh the checksum files for the specified artifact files in the maven repository. Sometimes the checksum files are not matched with the artifacts by some reason, so this command will do the refresh to make it match again. It will calculate the checksums of all artifact files in the specified path and compare with the companied checksum files of the artifacts, if the checksum are not matched, they will be refreshed.
0 commit comments