Role.Get throws resource does not exist when trying to get existed role

[duclan2703]

Describe what happened

Recently in our project, when we try to create a read-only user from an existed role this error keeps coming up.

I'll leave a sample code to reproduces the issue below

Sample program

Avayler.IaC.SampleReadOnlyRds.zip

Log output

No response

Affected Resource(s)

No response

Output of pulumi about

CLI
Version 3.181.0
Go Version go1.24.4
Go Compiler gc

Plugins
KIND NAME VERSION
resource aws 6.32.0
resource aws-native 0.103.0
resource command 4.5.0
resource datadog 4.28.0
resource docker 4.5.4
resource docker-build 0.0.2
language dotnet unknown
resource postgresql 3.11.0
resource random 4.16.1

Host
OS Microsoft Windows 11 Pro
Version 10.0.26100 Build 26100
Arch x86_64

Dependencies:
NAME VERSION
Contrib.Grpc.Core.M1 2.41.0
Microsoft.Extensions.Configuration.Binder 7.0.4
Microsoft.Extensions.Configuration.EnvironmentVariables 7.0.0
Microsoft.Extensions.Configuration.Json 9.0.5
Microsoft.Extensions.DependencyInjection 7.0.0
Microsoft.SourceLink.AzureRepos.Git 8.0.0
Moq 4.18.4
Newtonsoft.Json 13.0.3
Pulumi 3.63.1
Pulumi.Aws 6.32.0
Pulumi.Command 4.5.0
Pulumi.Docker 4.5.4
Pulumi.DockerBuild 0.0.2
Pulumi.PostgreSql 3.11.0
Pulumi.Random 4.16.1
AutoFixture 4.17.0
coverlet.collector 3.1.2
FluentAssertions 6.8.0
Microsoft.NET.Test.Sdk 17.1.0
System.Net.Http 4.3.4
System.Text.RegularExpressions 4.3.1
xunit 2.4.1
xunit.runner.visualstudio 2.4.3
Pulumi.AwsNative 0.103.0
Avayler.Configuration 0.7.0
Pulumi.Datadog 4.28.0
Amazon.Lambda.Core 2.6.0
Amazon.Lambda.Serialization.SystemTextJson 2.4.4
AWSSDK.EC2 3.7.107.1
AWSSDK.Lambda 3.7.107
AWSSDK.SecretsManager 3.7.102.61
AWSSDK.SimpleSystemsManagement 3.7.104.50

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).

[corymhall]

@duclan2703 is this something you have successfully done before and has started to fail? If so, is there anything that have changed (e.g. versions, etc)?

[duclan2703]

@corymhall unfortunately not, I've just implemented all these things recently, the role was created long time ago but now we are just now using it.

[guineveresaenger]

Hi @duclan2703 - this possibly feels like perhaps a permission setup bug on your end?

It's fairly difficult for us to see what is happening without the complete setup story.

Rather than uploading a tarball, could you link us to a Gist that contains:

1. your program
2. the setup of the pre-existing Role
3. the error log output of pulumi up --logtostderr --logflow -v=10 2> out.txt

For general setup questions, we encourage you to ask in our community Slack for help.