[Bug]: authentik_core_resources "Provider produced inconsistent final plan"

[jlevydev]

Prior Search

• I have already searched this project's issues to determine if a bug report has already been made.

What happened?

When attempting to re-apply the authentik_core_resources module I got the following output. Odd because when looking at the module a sort seems to already be in place to resolve this issue, but maybe there's a manual step I have to do here to fix. Uncertain why the sort isn't solving on its own. This is on the latest stable release (24-05.0).

Steps to Reproduce

Apply the authentik_core_resources module in such a way that it either adds to or changes the order of the authenticator validator stages

Version

main (development branch)

Relevant log output

No response

[fullykubed]

Interesting. This is definitely a bug in the upstream provider: goauthentik/terraform-provider-authentik#377. In fact, it is something I have already posted about in that thread.

If you 👍🏻 that thread, that will help create more visibility.

Here is my guess for what is happening:

1. When the resource is first created, the configuration_stages field is sorted in alphanum order.
2. When new stages are added, configuration_stages is sorted by when the stage was added.

Unfortunately, there isn't anything we can do to resolve the issue until the provider is fixed.

However, if you do a targeted delete of this resource and then a targeted apply, that may fix the issue you are experiencing personally.

I am going to leave this thread open until the upstream issue is resolved as a reminder for others who run into a similar issue.