Ignoring 409 errors in second attempt of creating api access

[gcornacchia]

in APIManagerAPIAccessAdapter during the creation of API Access if the server returns 409 status code (resource already exists) apim-cli intentionally ignores this error as the API access is already present.

If a retry is triggered due to "unknown API" error, the same check on 409 is not implemented.

This pull request aims to fix this situation.

[gcornacchia]

@rathnapandi

[gcornacchia]

hi @rathnapandi,
when are you planning to release the next version including this PR?

[rathnapandi]

Hi @gcornacchia,

I am planning to do a release at the end of next week.

[gcornacchia]

hi @rathnapandi, we need to test the next release, when will it be available?

[rathnapandi]

Hi @gcornacchia,

I am in the process of including one more fix.

Can you please test your fix and confirm -
axway-apimcli-1.14.9-SNAPSHOT.tar.gz

[gcornacchia]

Unfortunately, my fix wants to address a bug we found when upgrading from 1.14.2 to 1.14.6 and it's not easily reproducible.
If you have visibility you can check this Axway support case https://support.axway.com/en/case-center/view/id/01671223 with all the details.
@rathnapandi

[rathnapandi]

@gcornacchia,

The fix won't harm anything. I am done with my changes for the release, I will make sure all integration test passes and do the release tomorrow.

[rathnapandi]

Hi @gcornacchia,
I am facing the issue of publishing jar files to Maven repository (it is getting timed out). I will try again on Monday,

[rathnapandi]

Hi @gcornacchia,

I have published the release, please test, and let me know if you run into any issues.