https://pulumi.com logo
#general
Title
# general
m

most-mouse-38002

01/25/2024, 10:49 AM
Hello, we have a problem with the GitHub provider. We update an
ActionSecret
and Pulumi deletes it from the GitHub repository, but keeps it in the state claiming it has “replaced” it. It has not, it has nuked it, and then moved on. I see #250 on GitHub (pulumi/pulumi-github/) has a reference to
ActionsOrganizationSecret
from 2022, and the last comment from November has the same issue we are seeing. Since nobody is paying any attention to these issues on GitHub is there any known workaround or are we not using the provider correctly?
d

dry-keyboard-94795

01/25/2024, 12:02 PM
Thanks for reraising, hope it gets some visibility. Out of curiosity, does the same behaviour happen if you set
deleteBeforeReplace
? https://www.pulumi.com/docs/concepts/options/deletebeforereplace/
m

most-mouse-38002

01/25/2024, 12:27 PM
Will try that in a bit!
s

salmon-account-74572

01/25/2024, 4:39 PM
@most-mouse-38002 Would you mind also adding a comment to the issue, if using
deleteBeforeReplace
doesn’t fix it? (The issue mentions
deleteBeforeReplace
as a workaround.)
d

dry-keyboard-94795

01/25/2024, 4:51 PM
Forgot to post earlier, but the schema in the TF provider isn't quite right.
encryptedValue
is marked as
forceRecreate
, but the github api does support updating the value in place. This may be a better fix if it can be done on the pulumi side of the bridge
m

most-mouse-38002

02/07/2024, 10:30 AM
I’m not with this client anymore so sadly I cannot follow up on this.