-
Notifications
You must be signed in to change notification settings - Fork 41
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
PostgreSQL - simple resource change requires the resource to recreate and hits the quota on Azure West Europe #3961
Comments
Thank you for reporting this, @Karol-Pawlowski-Allegro. The current logic always uses PUT unless it's not even defined in the spec. This is due to the findings from #4 where PATCH was found to be insufficient and inconsistent. We'll probably need to look into hard-coding some exceptions, such as this one. |
thanks @thomas11. Is there a way I could mitigate the issue before it's addressed ? |
Unfortunately, I don't think there is one at this point. |
@thomas11, as you mentioned "hard-coding some exceptions", is it possible to modify the postgresql to support the patch method? I can try to handle it but I need some help where should I start. |
@thomas11 I had my hopes at dynamic provider but unfortunately saw it's not supported for C# yet. I guess, if we get a little assistance we could contribute |
I think #3983 should fix it. |
What happened?
Hi Guys,
We have a critical issue deploying PostgreSQL using Pulumi to WestEurope region. Due to the PostgreSQL implementation that uses PUT request method, we hit the region quota. The region has limited resources capacity and the quota may be hit when allocating new resources but that's not something we want to get now.
The change we want to apply is very straightforward and should not require any recreation (tags and credentials).
The error:
I have found the ticket: #4 that suggests the PUT should only be applied for resource creation, but don't see the PostgreSQL listed there.
Unfortunately, the migration to another region is not planned for the near future. Is there a way to perform the PATCH update for PostgreSQL or what is recommended way to mitigate the issue.
Example
postgreSQL_logs.txt
Output of
pulumi about
CLI
Version 3.150.0
Go Version go1.23.6
Go Compiler gc
Host
OS darwin
Version 14.7
Arch arm64
This project is written in dotnet: executable='/opt/homebrew/bin/dotnet' version='8.0.404'
Current Stack: organization/Devops.Examples/devops.dev
Found no resources associated with devops.dev
Found no pending operations associated with devops.dev
Backend
Name polpc13463
URL file://~
User karol.pawlowski
Organizations
Token type personal
No dependencies found
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).
The text was updated successfully, but these errors were encountered: