-
Notifications
You must be signed in to change notification settings - Fork 116
Adding support for ED25519 to all the *_cert resources
#173
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
Merged
Merged
Changes from 7 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
7b25ce5
Utilities for `*_cert` in `common_cert.go`, and utilities for `*_key`…
20b2e38
Replace all parsing of private keys with functions in `common_key.go`
39493a8
More moving key-specific utils in `common_key.go`
646291f
Deprecating `*_key_algorithm` arguments and making them optional as t…
e8836fe
Removing the use of `*_key_algorithm` from examples and tests for `*_…
e04daec
Regenerated doc
d4c8f05
Updated CHANGELOG for upcoming 3.2.0
14ab099
Deprecation tests
873f2c8
Tests to handle the before and after of `key_algorithm` deprecation
a698bdb
Remove mentions from the `Description` and `Deprecation` of the futur…
3410f9c
Reworked the logic for `parsePrivateKeyPEM` so it can accomodate all …
a7b7cf8
Regenerate doc
53b966e
To help with the deprecation of `key_algorithm`, setting it to `Optio…
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 deprecation seems to imply that this attribute should be available as read-only today too, so folks can update their configurations in preparation of the change. However, without calling
(ResourceData).Set()on the attribute, the only time it would be available for reference today is if it is configured and relying on the SDK's behavior of copying the attribute's planned value (from the configuration) to the state.My suggestion for these is to mark this attribute as
Computed: trueand calld.Set("key_algorithm", /*...*./)as appropriate. This removes any confusion about when the attribute value may be present, rather than it being dependent on the configuration. This will also ensure practitioners that remove the attribute from their configuration do not see an unexpected"whatever" -> nullplan when removing the configuration, since the attribute will remain in state in that case.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.
In my testing I concluded that a 2 step approach (first make it
Optional, release, then make itComputed) was necessary to avoid causing unnecessary re-creation of the resources.I can remove the reference to "future behaviour" as what matters is that ppl stop using it.
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 should've clarified better, sorry. I meant
OptionalandComputed, with callingd.Set().Optional+Computed+ForceNewshould not trigger recreation when removing the attribute from the configuration and if it does, that would be unexpected behavior we should investigate further.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.
So, here is the issue with adding
ComputertoOptionalnow: it will be a breaking change.I think we are expected to cross that bridge only once we release a major version, after a minor version with the deprecation - no?
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.
To be clear, I tried yesterday all the combinations, and just changing from
RequiredtoOptionalfor now, seemed like the only path forward to allow for an opt-in migration.All other options would end up with a breaking change.