to circle back to this release ther

Question

< limited rainbow 51650> to circle back to this release there is no new upstream release yet confused Your work is in master so we will wait for Julien to cut a new release maybe you can ask him slightly smiling face

limited-rainbow-51650 · Answer

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

limited-rainbow-51650 · Answer

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

limited-rainbow-51650 · Answer

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

broad-dog-22463 · Answer

We can of course cut against master

broad-dog-22463 · Answer

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

broad-dog-22463 · Answer

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 ```

broad-dog-22463 · Answer

and it is a legit bug in the provider

limited-rainbow-51650 · Answer

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

broad-dog-22463 · Answer

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

limited-rainbow-51650 · Answer

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

broad-dog-22463 · Answer

I just remember them changing the limits

broad-dog-22463 · Answer

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

broad-dog-22463 · Answer

< limited rainbow 51650> I think this might be the issue with delete

broad-dog-22463 · Answer

broad-dog-22463 · Answer

it actually does the delete later confused Not instantly

limited-rainbow-51650 · Answer

Hmm same is introduced for Groups in the latest Gitlab 12 8 <https docs gitlab com ee api groups html remove group>

broad-dog-22463 · Answer

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

broad-dog-22463 · Answer

we should just check for a response code

broad-dog-22463 · Answer

going to tweet Julien and copy you in

limited-rainbow-51650 · Answer

< broad dog 22463> 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

broad-dog-22463 · Answer

these are against public Gitlab SaaS

broad-dog-22463 · Answer

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

limited-rainbow-51650 · Answer

But paid account probably with Silver or Gold tier

broad-dog-22463 · Answer

probably

broad-dog-22463 · Answer

Even so the func should work the same across all tiers

limited-rainbow-51650 · Answer

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

broad-dog-22463 · Answer

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

broad-dog-22463 · Answer

unless there will be different providers for different levels

limited-rainbow-51650 · Answer

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

broad-dog-22463 · Answer

yeah that s a bad decision on their part IMO

limited-rainbow-51650 · Answer