The azure-sdk-for-ruby has been deprecated by Microsoft and we have forked it and maintained it separately. Since the old version of the SDK and the new forked sdk co-exists in the chef environment, having the same namespace conflicts. The gem namespace for the new version has been updated and this PR will update the code in this repo accordingly.
Issues Resolved
List any existing issues this PR resolves, or any Discourse or
StackOverflow discussions that are relevant
Description
The azure-sdk-for-ruby has been deprecated by Microsoft and we have forked it and maintained it separately. Since the old version of the SDK and the new forked sdk co-exists in the chef environment, having the same namespace conflicts. The gem namespace for the new version has been updated and this PR will update the code in this repo accordingly.
Issues Resolved
List any existing issues this PR resolves, or any Discourse or StackOverflow discussions that are relevant
Type of Change
Our release process assumes you are using Conventional Commit messages.
The most important prefixes you should have in mind are:
_fix_
: which represents bug fixes, and correlates to a SemVer patch._feat_
: which represents a new feature, and correlates to a SemVer minor._feat!_
:, orfix!:
,refactor!:
, etc., which represent a breaking change (indicated by the !) and will result in a major version change.If you have not included a conventional commit message this can be fixed on merge.
Check List