-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fixing readmes in resources #7163
Conversation
In Testing, Please Ignore[Logs] (Generated from 3e6ec14, Iteration 9).NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]
Python: test-repo-billy/azure-sdk-for-python [Logs]
Java: test-repo-billy/azure-sdk-for-java [Logs]
Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]
JavaScript: test-repo-billy/azure-sdk-for-js [Logs] [Diff]
|
Automation for azure-sdk-for-pythonA PR has been created for you: |
Automation for azure-sdk-for-goA PR has been created for you: |
Can one of the admins verify this patch? |
@lmazuel |
@@ -18,7 +18,6 @@ Generate all API versions currently shipped for this package | |||
|
|||
``` yaml $(java) && $(multiapi) | |||
batch: | |||
- tag: package-2019-06 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if there sdk released for this already? what's the impact of removing this line?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have added package-subscriptions-2019-06 below, so result is the same
@@ -40,24 +40,20 @@ tag: package-locks-2016-09 | |||
tag: package-policy-2019-06 | |||
``` | |||
|
|||
``` yaml $(package-policy) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was duplicated, and second has overwritten first resulting in wrong version included in some sdks
``` yaml $(package-resources) | ||
tag: package-resources-2019-08 | ||
``` | ||
|
||
``` yaml $(package-subscriptions) | ||
tag: package-subscriptions-2018-06 | ||
tag: package-subscriptions-2019-06 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's the sorting order? it's a mess now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what do you mean, there's only one tag in here?
@@ -25,7 +25,6 @@ batch: | |||
- tag: package-locks-2016-09 | |||
- tag: package-locks-2015-01 | |||
- tag: package-managedapplications-2018-06 | |||
- tag: package-managedapplications-2017-09 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why this tag is removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
because managedapplications was intentionally generated as single-api, and the second tag was put by mistake here by service team.
basically, in current configuration package-managedapplications-2017-09 will overwrite package-managedapplications-2018-06 meaning that old package was released instead of new one.
so after discussing with @lmazuel I decided to leave it as single api and fix the problem introduced by the service team.
No description provided.