Hello @giacomosirri and thank you for this PR.
The need of TF implementation for IAM members is real and we need to work on it ASAP.
We will not accept the contribution as it stands because it would have implications on member feature's future that we see differently - for example we may implement a dedicated resource scaleway_iam_member. Someone from the Scaleway team will work on this resource in the next weeks.

The guest type will disappear in the next months, and the fields you mentioned that cannot be updated will be updatable in very soon too.

However, I would like to thank you for your contribution. Can you give me your Organization-id (here or on Slack Scaleway community - Cyril Scw) so that I can put a voucher on your Organization? Thanks again

Hello @crlptl,
Thank you very much for the feedback and the kind voucher proposal. I understand what you mean, it is a complex matter that probably requires more careful considerations, so I look forward to see these features fully implemented.

Anyway, the organization id is: daf36079-e52c-416c-9535-d06742e48acc.

Btw, I also tried to access the slack community from the link in the footer of the website, but it appears to be broken:

Thank you again.

Hello @giacomosirri, after careful consideration it happens that your approach fits well the current API state and is future proof.
I re open your PR and will make a few suggestions if you are still willing to submit it.
Thank you.

Hello @Gnoale, thank you for the update, that's good to hear!
I will take the time to work on it and update the code based on your suggestions. I might be able to submit it within this week, at the latest next week.

@Gnoale @remyleone hello,
I'm pinging you here just to let you know that I have implemented the requested changes.
The acceptance tests were all ok and as far as I can tell now everything works pretty much as I would expect. However, if you notice something wrong, please let me know so that I can fix it!
Thank you

@Gnoale @remyleone hello,
I have updated again the implementation so that it now fully matches the API. I have also made minor changes to the documentation, now it should be a bit more clear. Let me know if it's ok for merging.
Thank you