Skip to content

Updating external_apple_secret shows outdated tokenΒ #211

@diederich

Description

@diederich

Bug report

  • I confirm this is a bug with Supabase, not with my own application.
  • I confirm I have searched the Docs, GitHub Discussions

Describe the bug

We're managing most settings via the terraform provider, which is fantastic - thanks for providing this! πŸ™
While updating the external_apple_secret for "Sign in with Apple" we found that there seems to be an old key cached somewhere. Supabase Dashboard already shows the new key, we have the new key in terraform, but a terraform plan shows us the old key and thus brings up a diff. (Applying that diff works, and nothing actually changes)

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

  1. Make sure supabase is configured with an external_apple_secret
  2. Make sure you have a proper terraform setup and terraform plan is showing an empty diff on apply/plan
  3. update the external_apple_secret in the Supabase Dashboard
  4. update the external_apple_secret in terraform
  5. Run terraform plan
  6. There's a diff visible, showing an old external_apple_secret, which is neither in code nor in Supabase anymore.

Expected behavior

The terraform diff should show up empty.

Screenshots

n/a

System information

  • OS: macOS
  • terraform provider version: 1.4.2
  • terraform version: 1.9.8

Additional context

This isn't blocking anything for us, more of an FYI. Once the new diff is applied, this also works correctly. It just seems it's comparing against the terraform state / cached version. If this is on purpose, e.g. because those credentials can't be read back, maybe there's a world to highlight that?
Thank you! πŸ™

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions