New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement Checksums and Signatures to allow for protecting against collisions of resources #7

Open

the-avid-engineer opened this issue Apr 11, 2023 · 0 comments

Owner

the-avid-engineer commented Apr 11, 2023 •

edited

Loading

Solves #2

Deployment would store some kind of metadata that can be retrieved before deployment for existing stacks.

A Checksum can always be generated from the request to update the template.

A Signature can be generated if the CLI is given a private key by cryptographically hashing the Checksum.

dotnet <tool> deploy <configuration key> --signing-key <private key>

If a Signing Key is given, then before deploying an existing stack, verify the stack's signature against the checksum using the signing key.

If the deployment does not have a Signature, continue with deployment
If deployment has a Signature, but it doesn't match the Checksum, the deployment is aborted

As part of deployment:

Generate a Checksum and persist it to the stack
If a Signing Key is given, generate a Signature and persist it to the stack

AWS CloudFormation

Perhaps use reserved Tags deploy:Checksum and deploy:Signature?

The text was updated successfully, but these errors were encountered:

the-avid-engineer changed the title ~~Implement Deployment Signing to allow for protecting against collisions and prevent back-to-back deployments causing unnecessary waiting cycles.~~ Implement Checksums and Signatures to allow for protecting against collisions and prevent back-to-back deployments causing unnecessary waiting cycles.

the-avid-engineer changed the title ~~Implement Checksums and Signatures to allow for protecting against collisions and prevent back-to-back deployments causing unnecessary waiting cycles.~~ Implement Checksums and Signatures to allow for protecting against collisions and prevent back-to-back deployments from unnecessarily extending waiting cycles.

the-avid-engineer changed the title ~~Implement Checksums and Signatures to allow for protecting against collisions and prevent back-to-back deployments from unnecessarily extending waiting cycles.~~ Implement Checksums and Signatures to allow for protecting against collisions of resources

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment