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

Application incorrectly being marked as different #1685

Open
barclayadam opened this issue Dec 18, 2024 · 3 comments
Open

Application incorrectly being marked as different #1685

barclayadam opened this issue Dec 18, 2024 · 3 comments
Labels
awaiting-feedback Blocked on input from the author kind/bug Some behavior is incorrect or out of spec

Comments

@barclayadam
Copy link

Describe what happened

An Application resource constantly updates due to changes, so it performs an API call which wipes out our "single page application" redirect uris (that have been specified elsewhere)

We use Automation API, so can see the diff looking for resourcePreEvent. In that event I can see that no detailedDiff has been created, and looking at the old and new two differences exist. The one below (new.id is empty) and the outputs (the new object is completely empty)

Image

I have added id to the ignoreChanges but it makes no difference

Sample program

I've not yet produced a minimum program that replicates this issue every time. We have some other applications in the same stack that do not have this issue

Log output

No response

Affected Resource(s)

azuread.Application

Output of pulumi about

CLI
Version 3.140.0
Go Version go1.23.3
Go Compiler gc

Plugins
KIND NAME VERSION
resource azure 4.37.0
resource azure-native 2.72.0
resource azuread 6.0.2
resource cloudflare 5.43.1
resource docker-build 0.0.7
resource kubernetes 4.15.0
resource newrelic 5.10.0
language nodejs unknown
resource random 4.0.0
resource tls 4.0.0

Host
OS Microsoft Windows 11 Pro
Version 10.0.22631 Build 22631
Arch x86_64

This project is written in nodejs: executable='C:\Program Files\nodejs\node.exe' version='v22.1.0'

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@barclayadam barclayadam added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Dec 18, 2024
@thomas11
Copy link
Contributor

Hi @barclayadam, without a repro it's hard to say why Pulumi thinks it should recreate the Application.

If it has to do with the Application and ApplicationRedirectUris resources, see #1686.

@thomas11 thomas11 added awaiting-feedback Blocked on input from the author and removed needs-triage Needs attention from the triage team labels Dec 19, 2024
@barclayadam
Copy link
Author

I guess it's possible that is what causes the issue as that is the only application instance that uses ApplicationRedirectUri resource, although hard to say because Pulumi is not outputting the actual reason it thinks there is a diff, and the only thing I can see in the engine output is as above that the id is changing.

Not sure if there is any way of getting more detail out of the engine? Not sure how it can detect a change, but not actually report said diff?

@pulumi-bot pulumi-bot added needs-triage Needs attention from the triage team and removed awaiting-feedback Blocked on input from the author labels Dec 19, 2024
@thomas11
Copy link
Contributor

Verbose logs might show more information. You might want to redact your subscription id before uploading.

A changing id suggests that one of the dynamic properties in the id have changed.

@thomas11 thomas11 added awaiting-feedback Blocked on input from the author and removed needs-triage Needs attention from the triage team labels Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-feedback Blocked on input from the author kind/bug Some behavior is incorrect or out of spec
Projects
None yet
Development

No branches or pull requests

3 participants