Skip to content
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

Add expiration support to pingone_credential_type resource and data source. #925

Open
mjspi opened this issue Nov 4, 2024 · 0 comments
Open
Labels
service/credentials PingOne Credentials size/medium Medium size change (e.g. enhancing the logic of an existing resource or datasource) status/blocked/upstream-sdk The issue/PR is blocked by an upstream SDK status/needs-triage The issue/PR needs initial triage type/enhancement New feature or request

Comments

@mjspi
Copy link
Contributor

mjspi commented Nov 4, 2024

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Properties that identify how to evaluate a credential type's expiration date and time are now supported for credentials configured using management.mode = AUTOMATED.

New or Affected Resource(s)

  • pingone_credential_type - resource and data source

Potential Terraform Configuration

# Copy-paste your PingOne related Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

# Remember to replace any account/customer sensitive information in the configuration before submitting the issue
resource "pingone_credential_type" "my_credential_type" {
    # ... other configuration params
    management_mode = "AUTOMATED"

    expiration {
      type = "HARD"  # Use "SOFT" if you want a user-defined expiration field

      # Option 1: Define expiration based on a specific timestamp
      timestamp = "2024-12-31T23:59:59Z"  # Specify a fixed expiration date in ISO 8601 format

      # Option 2: Define expiration after a specific duration
      after {
        duration = 30               # Number of time units before expiration (e.g., 30 days)
        time_unit = "DAYS"     # Time unit (e.g., SECONDS, MINUTES, HOURS, DAYS)
      }

      # Option 3: Define expiration with a custom expression
      expression = "now() + 30d"  # Example PingOne Expression Language (PEL) expression for 30 days from now

      # Optional: Specify the field name for SOFT expiration types only
      field_name = "credential_expiration"  # Only required for SOFT expiration type
    }   
}

References

@mjspi mjspi added type/enhancement New feature or request service/credentials PingOne Credentials status/blocked/upstream-sdk The issue/PR is blocked by an upstream SDK status/needs-triage The issue/PR needs initial triage size/medium Medium size change (e.g. enhancing the logic of an existing resource or datasource) labels Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service/credentials PingOne Credentials size/medium Medium size change (e.g. enhancing the logic of an existing resource or datasource) status/blocked/upstream-sdk The issue/PR is blocked by an upstream SDK status/needs-triage The issue/PR needs initial triage type/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant