/**
* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
* SPDX-License-Identifier: Apache-2.0.
*/
#pragma once
#include Describes a custom method used to code sign a file.See Also:
* AWS
* API Reference
The signature for the file.
*/ inline const CodeSigningSignature& GetSignature() const{ return m_signature; } /** *The signature for the file.
*/ inline bool SignatureHasBeenSet() const { return m_signatureHasBeenSet; } /** *The signature for the file.
*/ inline void SetSignature(const CodeSigningSignature& value) { m_signatureHasBeenSet = true; m_signature = value; } /** *The signature for the file.
*/ inline void SetSignature(CodeSigningSignature&& value) { m_signatureHasBeenSet = true; m_signature = std::move(value); } /** *The signature for the file.
*/ inline CustomCodeSigning& WithSignature(const CodeSigningSignature& value) { SetSignature(value); return *this;} /** *The signature for the file.
*/ inline CustomCodeSigning& WithSignature(CodeSigningSignature&& value) { SetSignature(std::move(value)); return *this;} /** *The certificate chain.
*/ inline const CodeSigningCertificateChain& GetCertificateChain() const{ return m_certificateChain; } /** *The certificate chain.
*/ inline bool CertificateChainHasBeenSet() const { return m_certificateChainHasBeenSet; } /** *The certificate chain.
*/ inline void SetCertificateChain(const CodeSigningCertificateChain& value) { m_certificateChainHasBeenSet = true; m_certificateChain = value; } /** *The certificate chain.
*/ inline void SetCertificateChain(CodeSigningCertificateChain&& value) { m_certificateChainHasBeenSet = true; m_certificateChain = std::move(value); } /** *The certificate chain.
*/ inline CustomCodeSigning& WithCertificateChain(const CodeSigningCertificateChain& value) { SetCertificateChain(value); return *this;} /** *The certificate chain.
*/ inline CustomCodeSigning& WithCertificateChain(CodeSigningCertificateChain&& value) { SetCertificateChain(std::move(value)); return *this;} /** *The hash algorithm used to code sign the file. You can use a string as the
* algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses SHA256 or SHA1, so you can pass
* either of them based on which was used for generating the signature.
The hash algorithm used to code sign the file. You can use a string as the
* algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses SHA256 or SHA1, so you can pass
* either of them based on which was used for generating the signature.
The hash algorithm used to code sign the file. You can use a string as the
* algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses SHA256 or SHA1, so you can pass
* either of them based on which was used for generating the signature.
The hash algorithm used to code sign the file. You can use a string as the
* algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses SHA256 or SHA1, so you can pass
* either of them based on which was used for generating the signature.
The hash algorithm used to code sign the file. You can use a string as the
* algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses SHA256 or SHA1, so you can pass
* either of them based on which was used for generating the signature.
The hash algorithm used to code sign the file. You can use a string as the
* algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses SHA256 or SHA1, so you can pass
* either of them based on which was used for generating the signature.
The hash algorithm used to code sign the file. You can use a string as the
* algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses SHA256 or SHA1, so you can pass
* either of them based on which was used for generating the signature.
The hash algorithm used to code sign the file. You can use a string as the
* algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses SHA256 or SHA1, so you can pass
* either of them based on which was used for generating the signature.
The signature algorithm used to code sign the file. You can use a string as
* the algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses ECDSA or RSA, so you can pass
* either of them based on which was used for generating the signature.
The signature algorithm used to code sign the file. You can use a string as
* the algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses ECDSA or RSA, so you can pass
* either of them based on which was used for generating the signature.
The signature algorithm used to code sign the file. You can use a string as
* the algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses ECDSA or RSA, so you can pass
* either of them based on which was used for generating the signature.
The signature algorithm used to code sign the file. You can use a string as
* the algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses ECDSA or RSA, so you can pass
* either of them based on which was used for generating the signature.
The signature algorithm used to code sign the file. You can use a string as
* the algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses ECDSA or RSA, so you can pass
* either of them based on which was used for generating the signature.
The signature algorithm used to code sign the file. You can use a string as
* the algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses ECDSA or RSA, so you can pass
* either of them based on which was used for generating the signature.
The signature algorithm used to code sign the file. You can use a string as
* the algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses ECDSA or RSA, so you can pass
* either of them based on which was used for generating the signature.
The signature algorithm used to code sign the file. You can use a string as
* the algorithm name if the target over-the-air (OTA) update devices are able to
* verify the signature that was generated using the same signature algorithm. For
* example, FreeRTOS uses ECDSA or RSA, so you can pass
* either of them based on which was used for generating the signature.