No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I did: <https://github.com/terraform-providers/terraform-provider-gitlab/pull/259#issuecomment-589954013>
Meanwhile, I wanted to know if Pulumi could create a release even if there is no TF provider release tagged. If not, is this a process issue or a technical issue?

My contribution started on 15 Jan. I hope you understand I’m a bit impatient by now. :wink:

I have the impression that Julien wants to get to the bottom of the test failures first before creating a new TF provider release. But this could still take a while…

but if there are test failures, then it could be a legit bug

this is my test failure:

```[ pulumi-gitlab/examples/project ]     error: deleting urn:pulumi:p-it-travis-job-project-a8b35cfc::label-gitlab::gitlab:index/project:Project::example-project: error waiting for project (16618257) to become deleted: timeout while waiting for state to become 'Deleted' (last state: 'Deleting', timeout: 10m0s)```

It is strange though that I only have an error in the TF tests on deleting a Group. And only a single failure.

I started seeing this error when I saw GitLab changed their API

Where in the release notes can I identify the changes to the API?
<https://about.gitlab.com/releases/>

I am running a test of this project and it's been "deleting" for 7 mins

<https://docs.gitlab.com/ee/api/projects.html#remove-project>

<@UK4HNFLCB> I *think* this might be the issue with delete

it actually does the delete later :confused: Not instantly

Hmm… same is introduced for Groups in the latest Gitlab 12.8
<https://docs.gitlab.com/ee/api/groups.html#remove-group>

this makes the check in the delete for it being deleted, pointless

<@UHTP242EB> do you run the pulumi-gitlab tests against your internal Gitlab setup? Is this the Premium or Ultimate tier? In these tiers projects are “soft”-deleted and your 10m timeout won’t suffice.

even so, it's a pointless check in the Delete as some uses may not have the time changed

But paid account probably with Silver or Gold tier?

Even so, the func should work the same across all tiers

No longer it seems. Functionality is different based on the tier you are on.

What I mean is, the TF provider has to work the same across them all

unless there will be different providers for different levels

This is going to become difficult as the D in CRUD is no longer deterministic in behavior. :disappointed:

yeah... that's a bad decision on their part IMO

<https://gitlab.com/gitlab-org/gitlab/issues/32935#note_293827289>