It is possibe for the user to override te etcd version, thus download a
different etcd file, but the checksum is constant, so the checksum
verification will fail in that case.
Added the ability to specify a different checksum, so the user would be
able to specify the new version checksum
Change-Id: I85af3af841ae957964f18d4e37a86ab0703882bc
Closes-Bug: #1736718
... | ... |
@@ -720,11 +720,11 @@ EXTRA_CACHE_URLS="" |
720 | 720 |
|
721 | 721 |
# etcd3 defaults |
722 | 722 |
ETCD_VERSION=${ETCD_VERSION:-v3.1.10} |
723 |
-ETCD_SHA256_AMD64="2d335f298619c6fb02b1124773a56966e448ad9952b26fea52909da4fe80d2be" |
|
723 |
+ETCD_SHA256_AMD64=${ETCD_SHA256_AMD64:-"2d335f298619c6fb02b1124773a56966e448ad9952b26fea52909da4fe80d2be"} |
|
724 | 724 |
# NOTE(sdague): etcd v3.1.10 doesn't have anything for these architectures, though 3.2.x does. |
725 |
-ETCD_SHA256_ARM64="" |
|
726 |
-ETCD_SHA256_PPC64="" |
|
727 |
-ETCD_SHA256_S390X="" |
|
725 |
+ETCD_SHA256_ARM64=${ETCD_SHA256_ARM64:-""} |
|
726 |
+ETCD_SHA256_PPC64=${ETCD_SHA256_PPC64:-""} |
|
727 |
+ETCD_SHA256_S390X=${ETCD_SHA256_S390X:-""} |
|
728 | 728 |
# Make sure etcd3 downloads the correct architecture |
729 | 729 |
if is_arch "x86_64"; then |
730 | 730 |
ETCD_ARCH="amd64" |