Automaion Api Random Deployment#instance errors
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 85
- Forks
- 26
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 22
Description
What happened?
We have a non-reproducable issue, which happens once a while every plan/up operation using automation api.
We have an inline program, which some times errors out with Trying to acquire Deployment#instance before 'run'.
This isn't really reproducable because it happens incosistantly.
Im really sure how to solve, this or even how to debug.
I wanted to see if anyout can provide insight on why this could happen, and if something could be attributing to this issue, especially it being inconsistent.
Example
The only special or "unique" thing im doing which could be a cause for the issue, is that my first defined resource which is seeing this error is a stack reference, seeing as a StackReference is just a CustomResource, I don't think this is relevant.
Output of pulumi about
CLI
Version 3.212.0
Go Version go1.25.5
Go Compiler gc
Host
OS nixos
Version 26.05 (Yarara)
Arch x86_64
Pulumi locates its logs in /tmp by default
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).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Automation API deployment lifecycle around the reported Deployment#instance error, using the inline program and StackReference case described in the issue. Reproduce or instrument the operation in the supplied Pulumi 3.212.0, Go 1.25.5, and NixOS environment; done means the inconsistent failure has a confirmed cause and a documented fix or diagnostic path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100