microscopic-xylophone-28322
12/19/2023, 11:09 AMpulumi up
this error shows up:
error: aws:codebuild/project:Project resource 'codebuild_finscore_v4' has a problem: expected project_visibility to be one of ["PUBLIC_READ" "PRIVATE"], got . Examine values at 'codebuild_finscore_v4.projectVisibility'.
I tried to import the resource then it turns out that the value of project_visibility
is empty string. So is there a way to tell Pulumi to just ignore that attribute? Thanksdry-keyboard-94795
12/19/2023, 12:13 PMdry-keyboard-94795
12/19/2023, 12:15 PMdry-keyboard-94795
12/19/2023, 12:16 PMpulumi import
isn't correctly generating code in this case to github please: https://github.com/pulumi/pulumi-aws/issuesmicroscopic-xylophone-28322
12/19/2023, 12:24 PMaws codebuild batch-get-projects --names <project_name>
, there is no projectVisibility
attribute for that project.microscopic-xylophone-28322
12/19/2023, 12:25 PMaws codebuild update-project-visibility --project-arn <proj_arn> --project-visibility PRIVATE --debug
, I got this errormicroscopic-xylophone-28322
12/19/2023, 12:26 PMignoreChanges
option but it doesn't help.dry-keyboard-94795
12/19/2023, 12:27 PMmicroscopic-xylophone-28322
12/19/2023, 12:28 PMdry-keyboard-94795
12/19/2023, 12:30 PMdry-keyboard-94795
12/19/2023, 12:32 PMmicroscopic-xylophone-28322
12/19/2023, 12:37 PMpulumi up
it shows an error.microscopic-xylophone-28322
12/19/2023, 12:37 PMopts=pulumi.ResourceOptions(
import_=project['service'],
ignore_changes=["projectVisibility"],
protect=False))
microscopic-xylophone-28322
12/19/2023, 12:38 PMproject['service']
is a string with the codebuild project name in itdry-keyboard-94795
12/19/2023, 12:38 PMmicroscopic-xylophone-28322
12/19/2023, 12:38 PMmicroscopic-xylophone-28322
12/19/2023, 12:39 PMproject_visibility
is emptydry-keyboard-94795
12/19/2023, 12:42 PMmicroscopic-xylophone-28322
12/19/2023, 1:26 PMmicroscopic-xylophone-28322
12/19/2023, 1:26 PMpulumi import
and it worked but with warningdry-keyboard-94795
12/19/2023, 1:28 PMignoreChanges
now that it's createdmicroscopic-xylophone-28322
12/19/2023, 1:28 PMpulumi up
again with this option:
ignore_changes=["projectVisibility"],
and it failed. It showed the error telling me about the projectVisibility
value not correct just like before.dry-keyboard-94795
12/19/2023, 1:30 PMpulumi stack import
dry-keyboard-94795
12/19/2023, 1:31 PMmicroscopic-xylophone-28322
12/19/2023, 1:31 PMmicroscopic-xylophone-28322
12/19/2023, 1:39 PMmicroscopic-xylophone-28322
12/19/2023, 1:42 PMpulumi refresh
, because I am curious whether the same problem will reoccur and it turns out it does. Is there any way to tell pulumi to ignore the projectVisiblity
attribute when we run pulumi refresh
?dry-keyboard-94795
12/19/2023, 1:42 PMmicroscopic-xylophone-28322
12/19/2023, 1:43 PMpulumi refresh
the projectVisibility
attribute is in the json filemicroscopic-xylophone-28322
12/19/2023, 1:44 PMdry-keyboard-94795
12/19/2023, 1:45 PMmicroscopic-xylophone-28322
12/19/2023, 1:46 PMmicroscopic-xylophone-28322
12/19/2023, 1:51 PMmicroscopic-xylophone-28322
12/19/2023, 1:52 PMpulumi up
then I am back to the previous errordry-keyboard-94795
12/19/2023, 1:54 PMignoreChanges
was supposed to also prevent property refreshes too.
The underlying bug needs reporting on github regardlessmicroscopic-xylophone-28322
12/19/2023, 1:55 PMdry-keyboard-94795
12/19/2023, 1:55 PMmicroscopic-xylophone-28322
12/19/2023, 1:55 PMdry-keyboard-94795
12/19/2023, 1:56 PMmicroscopic-xylophone-28322
12/19/2023, 2:22 PMdry-keyboard-94795
12/19/2023, 2:24 PMdry-keyboard-94795
12/19/2023, 2:40 PMmicroscopic-xylophone-28322
12/19/2023, 2:50 PM