Hey there 👋 , I'm happily using https://github.com/pulumiverse/pulumi-scaleway/ since 3 months now. When we choose to use it the maintenance was really good. During the last two months I notice that it doesn't seems to be maintained anymore. For example: • last commit have 2 months • 4 versions behind TF Scaleway provider, Pulumi Bridge and SDK begin to be old. • Github actions upgrade provider and upgrade bridge doesn't work since one month (gh creds issue): https://github.com/pulumiverse/pulumi-scaleway/actions/workflows/upgrade-provider.yml and https://github.com/pulumiverse/pulumi-scaleway/actions/workflows/upgrade-bridge.yml @limited-rainbow-51650 do you plan to continue the maintenance of this provider? (we need to know if we can continue to use Pulumi). I begin to search a way to help but it doesn't seems to be easy. To give you an example I tried this on my fork:

upgrade-provider probabl-ai/pulumi-scaleway

I from errors to errors on the tfgen step. I don't really know why but I need to update the provider/resources.go file manually to remove this errors. Example I already this errors:

error: failed to gather package metadata: problem gathering resources: 8 errors occurred:
        * TF resource "scaleway_tem_webhook" not mapped to the Pulumi provider
        * TF resource "scaleway_vpc_route" not mapped to the Pulumi provider
        * Pulumi token "scaleway:index/documentdbDatabase:DocumentdbDatabase" is mapped to TF provider resource "scaleway_documentdb_database", but no such resource found. The mapping will be ignored in the generated provider
        * Pulumi token "scaleway:index/documentdbInstance:DocumentdbInstance" is mapped to TF provider resource "scaleway_documentdb_instance", but no such resource found. The mapping will be ignored in the generated provider
        * Pulumi token "scaleway:index/documentdbPrivateNetworkEndpoint:DocumentdbPrivateNetworkEndpoint" is mapped to TF provider resource "scaleway_documentdb_private_network_endpoint", but no such resource found. The mapping will be ignored in the generated provider
        * Pulumi token "scaleway:index/documentdbPrivilege:DocumentdbPrivilege" is mapped to TF provider resource "scaleway_documentdb_privilege", but no such resource found. The mapping will be ignored in the generated provider
        * Pulumi token "scaleway:index/documentdbReadReplica:DocumentdbReadReplica" is mapped to TF provider resource "scaleway_documentdb_read_replica", but no such resource found. The mapping will be ignored in the generated provider
        * Pulumi token "scaleway:index/documentdbUser:DocumentdbUser" is mapped to TF provider resource "scaleway_documentdb_user", but no such resource found. The mapping will be ignored in the generated provider       


make: *** [Makefile:35: tfgen] Error 255

Now I only have this new one (scaleway_registry_image_tag exist in provider/resources.go):

error: failed to gather package metadata: problem gathering resources: 1 error occurred:
        * Pulumi token "scaleway:index/registryIamgeTag:RegistryIamgeTag" is mapped to TF provider resource "scaleway_registry_image_tag", but no such resource found. The mapping will be ignored in the generated provider

you can check my changes here https://github.com/probabl-ai/pulumi-scaleway/commit/d2f65c9f4724d2244843b267f9be9137dc17cbae • Why provider/resources.go should be change manually? • Could you please provide some help?

@stocky-coat-90951 first off: I will definitely continue to maintain the Scaleway provider! However, let me sketch you what I have been working on: the build workflows in a third-party package can't benefit from the same level off automation that the Pulumi providers team is using for now. This automation lives in https://github.com/pulumi/ci-mgmt/ Without this automation, it is quite tedious to keep a provider up to date. In the past few weeks, I have been working together with the Pulumi providers team to add support in the

ci-mgmt

repository for generating the Github Action workflows of thirdparty providers too. I'm almost full circle in such a setup. You can see some of the results in the following 2 repositories: • https://github.com/pulumiverse/pulumi-acme • https://github.com/pulumiverse/pulumi-matchbox Once I have the last bits in

ci-mgmt

, I will roll it out for more providers I maintain within Pulumiverse,

pulumi-scaleway

being one of them. ETA: I'm looking at 1, maximum 2 weeks for this to happen. I hope that's ok. 🙏🏼

@limited-rainbow-51650 If you need some support to get things tested/done let me know.

Will do. The last set of changes is related to the

upgrade-provider

workflows, where also workflow related code is integrated into the

upgrade-provider

tool. The team is discussing what should be done, and I will implement that.

Will there be a guidance for other maintainers on Pulumiverse how to integrate

ci-mgmt

into their provider repos?

Yes. The idea is to first add generic info in the README of

ci-mgmt

, then add Pulumiverse specifics on our side.

Sounds great 👍🏻

@stocky-coat-90951 https://github.com/pulumiverse/pulumi-scaleway/releases/tag/v1.16.0

thank you very much! 👍