docs(iam): document using expires_at with time_rotating #2677
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.
Hey there!
This PR adds a doc item for
iam_api_key
to show the use of theexpires_at
parameter in combination withtime_rotating
Reasoning for Change:
In my opinion, it could be interesting to document the proper usage of the
expires_at
parameter for API keys, as it's not super clear.Prefer Scaleway Documentation:
In that case, it's a pretty Terraform-specific use case. On the console, the API creation modal uses the "duration" of the key as opposed to the
expires_at
parameter.Terraform Configuration Language Features:
It's not ideal indeed to use a resource from a default provider, but in that case, it's the most proper way to use
expires_at
.Feel free to close this PR if you disagree with the change.
Have a great day 💜