-
Notifications
You must be signed in to change notification settings - Fork 63
Peng-7929:TerraformSDK_apikey_expiry #374
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 all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
0c81927
Update ns1-go SDK to v2.18.0 for API key expiry support
soniafrancisNS1 466f354
Add expiry_duration and secrets fields to API key resource
soniafrancisNS1 0a67a1b
Add tests for API key expiry_duration functionality
soniafrancisNS1 4ab3708
Add example for API key with automatic secret rotation
soniafrancisNS1 5ff5ff6
Update API key documentation for expiry_duration and secrets
soniafrancisNS1 ff1838c
Update CHANGELOG for v2.9.0 with API key expiry features
soniafrancisNS1 2ffc4fc
fix docs, add error handling, add validation tests
soniafrancisNS1 fdb838e
Update API key expiry changelog
soniafrancisNS1 64f808a
Update API key expiry example
soniafrancisNS1 cb45328
Relax expiry duration validation
soniafrancisNS1 09d6f18
Add custom expiry duration test
soniafrancisNS1 dc9cb6b
Update API key expiry docs
soniafrancisNS1 ebb0123
update the release date
soniafrancisNS1 5fb2497
Fix validation test to accept any days
soniafrancisNS1 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
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.
What is this testing? I don't think we can change the expiry duration on an api key once it's created.
(Edit - I realised that since terraform will recreate the object this probably does work, I'm not sure it's much use because of the key value changing. I think this is probably fine as it's just the way terraform works, customers should probably avoid doing it but we already have this for normal keys above.)
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.
Since Terraform recreates the resource when expiry_duration changes, technically the update works, but the API key/secrets will change as part of the recreation. I added a note in the docs to make that behaviour clearer