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

add readme.java.md and modify readme files #18492

Merged
merged 2 commits into from
May 25, 2022
Merged

add readme.java.md and modify readme files #18492

merged 2 commits into from
May 25, 2022

Conversation

Noelin
Copy link
Contributor

@Noelin Noelin commented Mar 31, 2022

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Changelog

Add a changelog entry for this PR by answering the following questions:

  1. What's the purpose of the update?
    • new service onboarding
    • new API version
    • update existing version for new feature
    • update existing version to fix swagger quality issue in s360
    • Other, please clarify
  2. When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
  3. When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
  4. If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.
    • SDK of .NET (need service team to ensure code readiness)
    • SDK of Python
    • SDK of Java
    • SDK of Js
    • SDK of Go
    • PowerShell
    • CLI
    • Terraform
    • No refresh required for updates in this PR

Contribution checklist:

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

Applicability: ⚠️

If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

  • Change to data plane APIs
  • Adding new properties
  • All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

  • Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

    • Adding a new service
    • Adding new API(s)
    • Adding a new API version
      -[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
  • Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

  • If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist

If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

  • Removing API(s) in a stable version
  • Removing properties in a stable version
  • Removing API version(s) in a stable version
  • Updating API in a stable or public preview version with Breaking Change Validation errors
  • Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.

Please follow the link to find more details on PR review process.

@Noelin Noelin requested a review from qiaozha as a code owner March 31, 2022 03:54
@openapi-workflow-bot
Copy link

Hi, @Noelin Thanks for your PR. I am workflow bot for review process. Here are some small tips.

  • Please ensure to do self-check against checklists in first PR comment.
  • PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging.
  • For specs comparison cross API versions, Use API Specs Comparison Report Generator
  • If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. How to fix?

  • Any feedback about review process or workflow bot, pls contact swagger and tools team. [email protected]

    @openapi-workflow-bot
    Copy link

    [Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks.

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Mar 31, 2022

    Swagger Validation Report

    ️️✔️BreakingChange succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️LintDiff succeeded [Detail] [Expand]
    Validation passes for LintDiff.

    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️~[Staging] ApiReadinessCheck succeeded [Detail] [Expand]
    ️️✔️ModelValidation succeeded [Detail] [Expand]
    Validation passes for ModelValidation.
    ️️✔️SemanticValidation succeeded [Detail] [Expand]
    Validation passes for SemanticValidation.
    ️️✔️Cross-Version Breaking Changes succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️️✔️SDK Track2 Validation succeeded [Detail] [Expand]
    Validation passes for SDKTrack2Validation
    ️️✔️PrettierCheck succeeded [Detail] [Expand]
    Validation passes for PrettierCheck.
    ️️✔️SpellCheck succeeded [Detail] [Expand]
    Validation passes for SpellCheck.
    ️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
    Validation passes for Lint(RPaaS).
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Mar 31, 2022

    Swagger Generation Artifacts

    ️️✔️ApiDocPreview succeeded [Detail] [Expand]
    ️❌SDK Breaking Change Tracking failed [Detail]

    Breaking Changes Tracking

    ️✔️azure-sdk-for-go - preview/fluidrelay/mgmt/2021-06-15-preview/fluidrelay - v63.3.0
    ️✔️azure-sdk-for-go - preview/fluidrelay/mgmt/2021-03-12-preview/fluidrelay - v63.3.0
    azure-sdk-for-python-track2 - track2_azure-mgmt-fluidrelay - Approved - 1.0.0b1
    +	Operation FluidRelayServersOperations.create_or_update has a new parameter fluid_relay_server_name
    +	Operation FluidRelayServersOperations.create_or_update no longer has parameter name
    +	Operation FluidRelayServersOperations.delete has a new parameter fluid_relay_server_name
    +	Operation FluidRelayServersOperations.delete no longer has parameter name
    +	Operation FluidRelayServersOperations.get has a new parameter fluid_relay_server_name
    +	Operation FluidRelayServersOperations.get no longer has parameter name
    +	Operation FluidRelayServersOperations.get_keys has a new parameter fluid_relay_server_name
    +	Operation FluidRelayServersOperations.get_keys no longer has parameter name
    +	Operation FluidRelayServersOperations.regenerate_key has a new parameter fluid_relay_server_name
    +	Operation FluidRelayServersOperations.regenerate_key no longer has parameter name
    +	Operation FluidRelayServersOperations.update has a new parameter fluid_relay_server_name
    +	Operation FluidRelayServersOperations.update no longer has parameter name
    ️️✔️ azure-sdk-for-net-track2 succeeded [Detail] [Expand]
    ️️✔️ azure-powershell succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from 9a65970. SDK Automation 14.0.0
      command	sh ./tools/SwaggerCI/init.sh ../azure-powershell_tmp/initInput.json ../azure-powershell_tmp/initOutput.json
      command	pwsh ./tools/SwaggerCI/psci.ps1 ../azure-powershell_tmp/generateInput.json ../azure-powershell_tmp/generateOutput.json
    • ️✔️Az.FluidRelay [View full logs]  [Release SDK Changes]
    ️⚠️ azure-sdk-for-python-track2 warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from 9a65970. SDK Automation 14.0.0
      command	sh scripts/automation_init.sh ../azure-sdk-for-python_tmp/initInput.json ../azure-sdk-for-python_tmp/initOutput.json
      cmderr	[automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
      command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
      cmderr	[automation_generate.sh] npm notice
      cmderr	[automation_generate.sh] npm notice New minor version of npm available! 8.5.5 -> 8.10.0
      cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.10.0>
      cmderr	[automation_generate.sh] npm notice Run `npm install -g [email protected]` to update!
      cmderr	[automation_generate.sh] npm notice
    • ️✔️track2_azure-mgmt-fluidrelay [View full logs]  [Release SDK Changes] Breaking Change Detected
      info	[Changelog] **Features**
      info	[Changelog]
      info	[Changelog]   - Added operation group FluidRelayContainersOperations
      info	[Changelog]   - Model FluidRelayServerUpdate has a new parameter location
      info	[Changelog]   - Model Identity has a new parameter user_assigned_identities
      info	[Changelog]
      info	[Changelog] **Breaking changes**
      info	[Changelog]
      info	[Changelog]   - Operation FluidRelayServersOperations.create_or_update has a new parameter fluid_relay_server_name
      info	[Changelog]   - Operation FluidRelayServersOperations.create_or_update no longer has parameter name
      info	[Changelog]   - Operation FluidRelayServersOperations.delete has a new parameter fluid_relay_server_name
      info	[Changelog]   - Operation FluidRelayServersOperations.delete no longer has parameter name
      info	[Changelog]   - Operation FluidRelayServersOperations.get has a new parameter fluid_relay_server_name
      info	[Changelog]   - Operation FluidRelayServersOperations.get no longer has parameter name
      info	[Changelog]   - Operation FluidRelayServersOperations.get_keys has a new parameter fluid_relay_server_name
      info	[Changelog]   - Operation FluidRelayServersOperations.get_keys no longer has parameter name
      info	[Changelog]   - Operation FluidRelayServersOperations.regenerate_key has a new parameter fluid_relay_server_name
      info	[Changelog]   - Operation FluidRelayServersOperations.regenerate_key no longer has parameter name
      info	[Changelog]   - Operation FluidRelayServersOperations.update has a new parameter fluid_relay_server_name
      info	[Changelog]   - Operation FluidRelayServersOperations.update no longer has parameter name
    ️⚠️ azure-sdk-for-java warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from 9a65970. SDK Automation 14.0.0
      command	./eng/mgmt/automation/init.sh ../azure-sdk-for-java_tmp/initInput.json ../azure-sdk-for-java_tmp/initOutput.json
      command	./eng/mgmt/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json
      cmderr	[generate.py] SLF4J: Defaulting to no-operation (NOP) logger implementation
      cmderr	[generate.py] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
      cmderr	[generate.py] SLF4J: Defaulting to no-operation (NOP) logger implementation
      cmderr	[generate.py] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
    • ️✔️azure-resourcemanager-fluidrelay [View full logs]  [Release SDK Changes]
    ️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from 9a65970. SDK Automation 14.0.0
      command	sh ./eng/initScript.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json
      command	generator automation ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json
    • ️✔️preview/fluidrelay/mgmt/2021-06-15-preview/fluidrelay [View full logs]  [Release SDK Changes]
      info	[Changelog] This is a new package
      info	[Changelog]
    • ️✔️preview/fluidrelay/mgmt/2021-03-12-preview/fluidrelay [View full logs
      info	[Changelog] This is a new package
      info	[Changelog]
    ️⚠️ azure-sdk-for-js warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from 9a65970. SDK Automation 14.0.0
      command	sh .scripts/automation_init.sh ../azure-sdk-for-js_tmp/initInput.json ../azure-sdk-for-js_tmp/initOutput.json
      cmderr	[automation_init.sh] npm WARN deprecated [email protected]: The functionality that this package provided is now in @npmcli/arborist
      cmderr	[automation_init.sh] deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
      cmderr	[automation_init.sh]  @opentelemetry/[email protected]: Package renamed to @opentelemetry/api, see https://github.com/open-telemetry/opentelemetry-js
      cmderr	[automation_init.sh] WARN deprecated @azure/[email protected]: This version has been deprecated, please upgrade to the version tagged as latest
      cmderr	[automation_init.sh] npm WARN @octokit/[email protected] requires a peer of @octokit/core@>=3 but none is installed. You must install peer dependencies yourself.
      warn	File azure-sdk-for-js_tmp/initOutput.json not found to read
      command	sh .scripts/automation_generate.sh ../azure-sdk-for-js_tmp/generateInput.json ../azure-sdk-for-js_tmp/generateOutput.json
    • ️✔️@azure/arm-fluidrelay [View full logs]  [Release SDK Changes]
      info	[Changelog]
      error	breakingChangeTracking is enabled, but version or changelogItem is not found in output.
    Posted by Swagger Pipeline | How to fix these errors?

    @Noelin
    Copy link
    Contributor Author

    Noelin commented Mar 31, 2022

    @qiaozha,
    Do you know how to fix this issue for python and js?

    @Noelin
    Copy link
    Contributor Author

    Noelin commented Apr 1, 2022

    @qiaozha
    Is there any update?

    @qiaozha
    Copy link
    Member

    qiaozha commented Apr 2, 2022

    /azp run

    @azure-pipelines
    Copy link

    Azure Pipelines successfully started running 1 pipeline(s).

    @qiaozha
    Copy link
    Member

    qiaozha commented Apr 6, 2022

    @ruowan Can you take a look at the credscan failure ? Thanks

    @qiaozha
    Copy link
    Member

    qiaozha commented Apr 6, 2022

    @msyyc Can you help take a look at the Python SDK breaking change ? Thanks

    package-name: "fluidrelay"
    output-folder: "$(typescript-sdks-folder)/packages/fluidrelay"
    package-name: "@azure/arm-fluidrelay"
    output-folder: "$(typescript-sdks-folder)/packages/fluidrelay/arm-fluidrelay"
    Copy link
    Member

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Suggested change
    output-folder: "$(typescript-sdks-folder)/packages/fluidrelay/arm-fluidrelay"
    output-folder: "$(typescript-sdks-folder)/sdk/fluidrelay/arm-fluidrelay"

    Copy link
    Contributor Author

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    @qiaozha
    Just make a change.
    Could you take a look when you have time?

    @ghost
    Copy link

    ghost commented May 15, 2022

    Hi, @Noelin. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove no-recent-activity label.

    @ghost ghost added the no-recent-activity label May 15, 2022
    @Noelin
    Copy link
    Contributor Author

    Noelin commented May 24, 2022

    @qiaozha
    Could you approve the PR?

    @ghost ghost removed the no-recent-activity label May 24, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    3 participants