rich-exabyte-94739
12/02/2020, 10:33 PMpulumi up --yes
except that it seems to get stuck on @ Previewing update
. Is there any way we can debug this to see why it gets hung?rich-exabyte-94739
12/02/2020, 10:34 PMbumpy-laptop-30846
02/18/2021, 1:37 PMambitious-engine-25996
03/04/2021, 11:56 AMbuildAndPushImage
function when i run it in a gitlab pipeline it is failing with the following error
error: spawn docker ENOENT
error: Error: ' docker build ../gateway -t ca21c859-container' failed with exit code 1
Has anyone encountered this before? I suspect it is something to do with docker in docker but im not surebrainy-bear-32920
04/28/2021, 12:37 PMError processing webhook.
on gitlab.com when testing the merge request events.
Do you have any idea of steps to troubleshoot an issue like this?tall-beard-99429
05/07/2021, 5:33 PMtall-beard-99429
05/07/2021, 5:37 PMplain-quill-22197
07/05/2021, 4:46 PMplain-quill-22197
07/12/2021, 10:23 AMclever-sunset-76585
07/15/2021, 4:22 PMplain-quill-22197
07/19/2021, 12:41 PMrefined-kitchen-10197
07/23/2021, 12:09 AMbulky-area-51023
10/06/2021, 8:14 AMgit.<organization.name>.com
, and pulumi keeps redirecting to <http://gitlab.com|gitlab.com>
.tall-beard-99429
11/09/2021, 4:16 PMexport const packages = new gitlab.Group(`Group (${Group.packages})`, {
name: Group.packages,
path: Group.packages.toLowerCase().replace(' ', '-'),
autoDevopsEnabled: false,
emailsDisabled: false,
lfsEnabled: true,
mentionsDisabled: false,
projectCreationLevel: 'developer',
requireTwoFactorAuthentication: false,
requestAccessEnabled: true,
shareWithGroupLock: false,
parentId: 2376237, // Number(jobilla.id),
});
export const protos = new gitlab.Group(`Group (${Group.protos})`, {
name: Group.protos,
path: Group.protos.toLowerCase().replace(' ', '-'),
autoDevopsEnabled: false,
emailsDisabled: false,
lfsEnabled: true,
mentionsDisabled: false,
projectCreationLevel: 'developer',
requireTwoFactorAuthentication: false,
requestAccessEnabled: true,
shareWithGroupLock: false,
parentId: 10721813, // Number(packages.id),
});
These ID's (for parentId) are 100% correct. I can see them show the values that are currently hardcoded on app.pulumi.com and also in the export of the current state. However, if I try to use the value as shown by the comments, it tries to change the value to something completely different. The output is a string
but the input requires a number
, not sure if this is the cause of the problem. Anyone got a work around for me that isn't hardcoding the IDs?tall-beard-99429
11/09/2021, 4:21 PM~ protos : {
autoDevopsEnabled : false
emailsDisabled : false
~ fullName : "XXX / Packages / protos" => output<string>
~ fullPath : "XXX/packages/protos" => output<string>
~ id : "13229671" => output<string>
lfsEnabled : true
mentionsDisabled : false
name : "protos"
~ parentId : 1.0721813e+07 => -9.223372036854776e+18
path : "protos"
projectCreationLevel : "developer"
requestAccessEnabled : true
requireTwoFactorAuthentication: false
~ runnersToken : "XXXXXX" => output<string>
shareWithGroupLock : false
~ subgroupCreationLevel : "maintainer" => "owner"
twoFactorGracePeriod : 48
urn : "urn:pulumi:dev::git-managed::gitlab:index/group:Group::Group (protos)"
~ visibilityLevel : "private" => output<string>
~ webUrl : "<https://gitlab.com/groups/jobilla/packages/protos>" => output<string>
}
tall-beard-99429
11/09/2021, 4:29 PMpackages.id.apply(id => (id as unknown) as number),
Still believe this to be a bug of some kindlimited-battery-10877
02/07/2022, 11:15 AMSince last week, I'm facing the following issue :
Diagnostics:
pulumi:pulumi:Stack (gitlab-resources):
error: resource complete event returned an error: failed to save snapshot: [403] The provided update token has expired.
error: update failed
I tried to enable logs but I generate a file with almost 180k line, so it's pretty hard to find what's wrong inside.
I also try to debug by generating a tracing file following this https://www.pulumi.com/docs/troubleshooting/#performance. And after some diging i found that several process took more than one min
I try to change the parallelism to 1, 10 or 40 but nothing change, i still have the same error.
Is anyone facing the same issue ?
For information, my gitlab is an on-premise one, not gitlab.comstraight-cartoon-24485
02/12/2022, 11:01 PMlemon-monkey-228
05/01/2022, 1:53 PMProject
resource) is always seen as changedlemon-monkey-228
05/01/2022, 1:54 PM# pulumi preview
Previewing update (production):
Type Name Plan Info
pulumi:pulumi:Stack gitlab-production
└─ gitlab:index:Group redacted
└─ gitlab:index:Group devops
└─ gitlab:index:Group pulumi
~ └─ gitlab:index:Project pulumi-utils update [diff: ~mergePipelinesEnabled,mirror]
lemon-monkey-228
05/01/2022, 1:57 PMpulumi refresh
but it looks like it thinks I'm updating those settings every time.
# pulumi preview --diff
Previewing update (production):
pulumi:pulumi:Stack: (same)
[urn=urn:pulumi:production::gitlab::pulumi:pulumi:Stack::gitlab-production]
~ gitlab:index/project:Project: (update)
[id=35769935]
[urn=urn:pulumi:production::gitlab::gitlab:index/group:Group$gitlab:index/group:Group$gitlab:index/group:Group$gitlab:index/project:Project::pulumi-utils]
[provider=urn:pulumi:production::gitlab::pulumi:providers:gitlab::default_4_7_0::cc59570d-ef66-4687-9502-026519d672c6]
~ mergePipelinesEnabled: false => true
~ mirror : false => true
Resources:
~ 1 to update
If I check the stack file, under inputs
I see:
"mergePipelinesEnabled": true,
and it's true
in the TypeScript pulumi project I'm using toolemon-monkey-228
05/01/2022, 2:01 PMoutputs
section of my state, it says:
"mergePipelinesEnabled": false,
white-balloon-205
hundreds-megabyte-76150
05/17/2022, 5:17 PMError processing webhook.
Does anyone else have experience getting the webhook integration working so that pulumi can decorate merge requests?few-mechanic-54967
10/20/2022, 11:42 AMenvironment_scope=*
, I already run pulumi up
in dev
stack. After it, I change stack to `staging`and rerun pulumi up
, but there is try to create again(my expect is not create again because it already create when in `dev`stack).
Thank youstraight-cartoon-24485
01/25/2023, 4:31 PM