You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
Currently self-managed backend lock metadata contains only "Pid", "Username", "Hostname", "Timestamp". None of these are very useful for finding the real owner when Pulumi is run inside a container and/or part of an automation pipeline.
Would be helpful if one could add more specific information like commit ID, change ID, pipeline ID, "real" user etc. Even the "message" parameter content from "pulumi up" would suffice.
Affected area/feature
The text was updated successfully, but these errors were encountered:
Hello!
Issue details
Currently self-managed backend lock metadata contains only "Pid", "Username", "Hostname", "Timestamp". None of these are very useful for finding the real owner when Pulumi is run inside a container and/or part of an automation pipeline.
Would be helpful if one could add more specific information like commit ID, change ID, pipeline ID, "real" user etc. Even the "message" parameter content from "pulumi up" would suffice.
Affected area/feature
The text was updated successfully, but these errors were encountered: