-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Synthetic property preventing import #237
Comments
Thanks for the issue, @Raniz85. |
Hi @Raniz85. Thanks for letting us know about this. As a workaround, is it possible to leave |
Also, can you post the error you get when you run |
Yeah, we do that now but I'd rather not since that means someone has to remember to change that after importing or deleting the project will be final. I would expect this to work like The error I get is this:
|
Thanks. We're seeing the same issue you are. I'm not sure what the resolution will be here. The problem is that while you understand that I think that pulumi/pulumi#12042 is the most relevant issue in pulumi/pulumi. |
What happened?
We manage GitLab with a project that uses predefined building blocks that contain defaults that we don't want our developers to change. Among these we set archive_on_delete to prevent accidental deletion of projects.
This attribute however prevents us from importing existing projects since we can't import projects that have diffs and we can't set archive_on_delete since it's an attribute that is only set in the stack and not actually reflected in GitLab.
Expected Behavior
The import should succeed regardless of the value of archive_on_delete.
Steps to reproduce
True
and import_ to the ID of the project to import.pulumi up
Output of
pulumi about
CLI
Version 3.55.0
Go Version go1.20
Go Compiler gc
Plugins
NAME VERSION
gitlab 4.9.0
python unknown
Host
OS debian
Version bookworm/sid
Arch x86_64
This project is written in python: executable='/usr/bin/python3' version='3.10.6
'
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).
The text was updated successfully, but these errors were encountered: