Fernando de Oliveira

I agree with you @datianshi, I believe it's valuable providing the option of deploying ARO through Terraform even with this current limitation.

Well, apparently the new RHO version on the Azure SDK supports mutable worker profile attributes, see the `2022-04-01` version [here](https://github.com/Azure/azure-sdk-for-go/blob/main/services/redhatopenshift/mgmt/2022-04-01/redhatopenshift/models.go#L882). The previous `2020-04-30` version had immutable properties (details for comparison...

Awesome @datianshi, thanks for sharing this one! I'm working on updating the schema, CRUD methods and integration tests to match this new version. I'll keep you posted 😊.

Hey @tombuildsstuff @katbyte @datianshi the PR is ready to be reviewed again 😊. I've updated the code and documentation to match the `2022-04-01` schema and introduced new acceptance tests for...

> what stops this branch from being approved and merged? @tombuildsstuff wondering if you have any update on this review?

> not sure what client id it is referring to? @katbyte looking at the error message apparently we can't associate a service principal with multiple clusters (1-1 relationship). The options...

> @fedeoliv - we can run them sequentially, also if that is a service limitation we should document it in the docs Great, I updated the ARO documentation with a...

> @fedeoliv apologies for the contradiction - we can we update this to use a new Service Principal created as a part of each test - we can use the...

> s like the tests are failing due to only one cluster being allowed. is this a service limit that can be increased or Hey @katbyte, humm seems this is...

Hey everyone, JFYI I created a PR #1838 with a proposal for the Producer instrumentation.