Skip to content
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

Merged
merged 22 commits into from
Feb 17, 2021

Conversation

gapra-msft
Copy link
Member

@gapra-msft gapra-msft commented Jan 26, 2021

No description provided.

@ghost ghost added the Storage Storage Service (Queues, Blobs, Files) label Jan 26, 2021
@check-enforcer
Copy link

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:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

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 prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run java - [service] - ci

@gapra-msft
Copy link
Member Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@gapra-msft
Copy link
Member Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@gapra-msft
Copy link
Member Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines failed to run 1 pipeline(s).

@gapra-msft
Copy link
Member Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@gapra-msft
Copy link
Member Author

/azp run java - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

import java.time.OffsetDateTime;

/** The DirectoriesCreateHeaders model. */
@JacksonXmlRootElement(localName = "null")
Copy link
Contributor

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
Copy link
Contributor

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

Copy link
Member Author

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 {
Copy link
Contributor

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?

Copy link
Member Author

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

@gapra-msft gapra-msft merged commit 362e9c0 into Azure:master Feb 17, 2021
@gapra-msft gapra-msft deleted the storage/migrateFilesToNewGenerator branch February 17, 2021 22:51
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-java that referenced this pull request May 12, 2022
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants