Skip to content

Security Center - Removing properties to allow auto code generation#3453

Merged
hovsepm merged 2 commits intoAzure:masterfrom
chlahav:master
Jul 24, 2018
Merged

Security Center - Removing properties to allow auto code generation#3453
hovsepm merged 2 commits intoAzure:masterfrom
chlahav:master

Conversation

@chlahav
Copy link
Copy Markdown
Contributor

@chlahav chlahav commented Jul 19, 2018

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

@AutorestCI
Copy link
Copy Markdown

AutorestCI commented Jul 19, 2018

Automation for azure-sdk-for-python

Nothing to generate for azure-sdk-for-python

@AutorestCI
Copy link
Copy Markdown

AutorestCI commented Jul 19, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link
Copy Markdown

AutorestCI commented Jul 19, 2018

Automation for azure-sdk-for-go

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-go#2298

@chlahav chlahav force-pushed the master branch 3 times, most recently from c3d03a6 to 91612b8 Compare July 19, 2018 18:28
@AutorestCI
Copy link
Copy Markdown

AutorestCI commented Jul 19, 2018

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@AutorestCI
Copy link
Copy Markdown

AutorestCI commented Jul 19, 2018

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

@chlahav chlahav changed the title Security Cetner - Removing properties to allow auto code generation Security Center - Removing properties to allow auto code generation Jul 23, 2018
- make allOf on `object` not a `string`
- fix hostname to match examples
@vladbarosan
Copy link
Copy Markdown

@AutorestCI rebuild azure-sdk-for-go

@chlahav
Copy link
Copy Markdown
Contributor Author

chlahav commented Jul 24, 2018

thanks @vladbarosan.
I confirm that:

  1. “hostname” is the correct property name
  2. the “additionalProperties” was supposed to be removed

@hovsepm hovsepm merged commit 30d7f17 into Azure:master Jul 24, 2018
@vladbarosan
Copy link
Copy Markdown

@AutorestCI rebuild azure-sdk-for-go

@vladbarosan
Copy link
Copy Markdown

@AutorestCI rebuild azure-sdk-for-go

@vladbarosan
Copy link
Copy Markdown

@lmazuel so if you can help a little here. I updated Go generator version in the "latest" branch in the sdk repo. When executing again the rebuild command, should it use the new version there ? And are there any logs to see the build process ?

@jhendrixMSFT
Copy link
Copy Markdown
Member

@vladbarosan I think "regenerate" is the command you want but let's see what @lmazuel has to say.

@vladbarosan
Copy link
Copy Markdown

@AutorestCI regenerate azure-sdk-for-go

@vladbarosan
Copy link
Copy Markdown

@jhendrixMSFT it gave me a thumbs up so lets see :)

@vladbarosan
Copy link
Copy Markdown

didnt see to help :(, any suggestions @lmazuel ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants