Add test fcr

[tutkat]

For the PR were introduced changes:

• changed api client (okhttp on rest-assured) and regenerated all classes
• modified existing tests and adjusted for new client
• added tests for Cloud Router endpoints
• added test for Port endpoint
• added flow to run tests only

[thogarty]

@tutkat , please add descriptions of why you changed what you changed. The status update was confusing as well so it's important to add as much context as you can to whomever will be reviewing your code.

[thogarty]

It looks like this is a breaking change for existing users of the Java SDK. What will be the outcome to the user? Do they have to adjust their code based on this update?

We need to prevent breaking changes because our customers have to make many modifications as a result. We only make them if absolutely necessary and I still haven't seen enough evidence in your description to warrant the breaking change. What was the exact issue that okhttp-gson gave you that rest-assured is not?

[thogarty]

There was a change in this template to modify the default timeouts returned by the API Client. You'll need to maintain that same default in the rest-assured API client.

[tutkat]

what "default timeouts" you mean?

[thogarty]

Workflow needs to be modified based on comments.

[thogarty]

This is absolutely a breaking change requiring customer updates. Please provide ample evidence for this adjustment.

[tutkat]

It looks like this is a breaking change for existing users of the Java SDK. What will be the outcome to the user? Do they have to adjust their code based on this update?

We need to prevent breaking changes because our customers have to make many modifications as a result. We only make them if absolutely necessary and I still haven't seen enough evidence in your description to warrant the breaking change. What was the exact issue that okhttp-gson gave you that rest-assured is not?

I don't know the reason but this client wasn't able to execute POST calls. I'm sure any client didn't do that because someone reports that doesn't work. I spent few days to try to configure it but unfortunately I was forced to move to another http client.

actually users after upgrade their usage need to upgrade imports and one method to perform call. actually example is put to readme

[ctreatma]

I don't know the reason but this client wasn't able to execute POST calls.

How does this issue manifest? Are the requests never sent at all? Are they sent in an invalid format and failing? Is the API responding with an HTTP error? Are all POST calls impacted or only for particular endpoints? The metal-java SDK also uses okhttp-gson, and although metal-java is now defunct it was definitely used successfully to send POST requests, which indicates it should be possible for fabric-java to send POST requests successfully without introducing a breaking change to the client.

[thogarty]

@tutkat, please remove code generation from this PR. You need to figure out how to separate your test files from any changes you've made to the SDK during this time. There shouldn't be changes to 1,209 files just to add your tests.

[thogarty]

@tutkat , this PR cannot be reviewed until it has been trimmed.