-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Migrated file shares to new generator #18818
Migrated file shares to new generator #18818
Conversation
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
...gger/src/main/java/com/azure/storage/file/share/customization/ShareStorageCustomization.java
Outdated
Show resolved
Hide resolved
...file-share/src/main/java/com/azure/storage/file/share/specialized/ShareLeaseAsyncClient.java
Outdated
Show resolved
Hide resolved
/azp run java - storage - tests |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
...-share/src/main/java/com/azure/storage/file/share/implementation/models/CopyFileSmbInfo.java
Outdated
Show resolved
Hide resolved
...zure/storage/file/share/implementation/models/CustomFileAndDirectoryListingDeserializer.java
Show resolved
Hide resolved
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
import java.time.OffsetDateTime; | ||
|
||
/** The DirectoriesCreateHeaders model. */ | ||
@JacksonXmlRootElement(localName = "null") |
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 seems a little weird. I'm guessing its because this is actually deserializing headers and not xml?
@@ -644,21 +648,6 @@ directive: | |||
$["x-ms-parameter-location"] = "method"; | |||
``` | |||
|
|||
### Add the CustomFileAndDirectoryListingDeserializer attribute |
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 did we delete this? It looks like the custom deserializer is still there
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.
Deleted this and added it to the ShareStorageCustomization clas. This way no longer works with the new generator
/** | ||
* Customization class for File Share Storage. | ||
*/ | ||
public class ShareStorageCustomization extends Customization { |
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.
Is this something to do with the transforms?
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.
Yeah this is the new way to modify generated code
Review request for Microsoft.ContainerService to add version 2022-04-01 (Azure#18991) * Adds base for updating Microsoft.ContainerService from version stable/2022-03-01 to version 2022-04-01 * Updates readme * Updates API version in new specs and examples * update readme (Azure#18715) * add storage profile into managedcluster (Azure#18818) Signed-off-by: Ji An Liu <[email protected]> * GA mc alias minor version in 0401 (Azure#18821) * GA mc alias minor version in 0401 * unify info to be consistent with ap alias minor version * update the title of kuberneteVersion * add title for currentKubernetesVersion * make currentKubernetesVersion language consistency with AP currentOrchestratorVersion * GA agent pool alisa minor version (Azure#18814) * GA agent pool alisa minor version * Unify description with MC * Add read-only field * Rematch description with MC Co-authored-by: Xia ZHU <[email protected]> Co-authored-by: Ji'an Liu <[email protected]> Co-authored-by: Jianping Zeng <[email protected]> Co-authored-by: Thalia Wang <[email protected]>
No description provided.