-
Notifications
You must be signed in to change notification settings - Fork 22
doc(example): examples dir, and RawAESKeyring example #281
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.
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
Conversation
- Create examples directory and project - Create RawAESKeyringExample.cs - Create ExampleUtils.cs
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Co-authored-by: Matt Bullock <[email protected]>
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Co-authored-by: Matt Bullock <[email protected]>
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the qualifier that we need to remember to come back and add in the encryption context check, LGTM.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: we use the directory name "keyring" (singular) in Java and Python; we should be consistent.
examples/dotnet/README.md
Outdated
1. Each example file MUST contain exactly one example. | ||
1. Each example filename MUST be descriptive. | ||
1. Each example file MUST contain a public class matching the filename. | ||
1. Each example file MUST contain a method called `run` that runs the example. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This framing reads a bit wrong in this case since it's not a method on the file, it's a method on the class. Looking over at Java, we have a similar wording issue there.
examples/dotnet/README.md
Outdated
1. Each example filename MUST be descriptive. | ||
1. Each example file MUST contain a public class matching the filename. | ||
1. Each example file MUST contain a method called `run` that runs the example. | ||
1. Each example MUST be exercised by a `[Fact]` test method within its class. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't love this because it requires every example to repeat itself, but if this is the best way to approach this in .NET then ok.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's probably the simplest/fastest solution in most languages, and I'd rather have this working to unblock more examples with an issue to improve it if we feel strongly about it.
It will be important to have test coverage metrics for this csproj in particular, no matter how we run them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having said that, this documentation is inconsistent - the stuff about run
isn't sufficient, and not actually relevant since our CI assumes there's a [Fact]
that will run it instead. I'm going to remove the items that aren't true YET, and we can put them back if and when we put different CI into place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to keep the requirement of the entry point being named "run" so that we're consistent across languages.
I'm confident we'll cover that as part of awslabs/aws-encryption-sdk-specification#96 (i.e. #289) |
LGTM aside from @mattsb42-aws' latest suggestions! |
Co-authored-by: Matt Bullock <[email protected]>
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Co-authored-by: Matt Bullock <[email protected]>
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Issue #, if available: resolves #263
Description of changes: Created example directory and project, and created AES Example
Squash/merge commit message, if applicable:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.