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

Integrate Azure into GCP's magic-modules #14

Open
wants to merge 203 commits into
base: master
Choose a base branch
from
Open

Conversation

JunyiYi
Copy link
Collaborator

@JunyiYi JunyiYi commented Aug 6, 2019

In this PR, we integrate Azure-specific logic and coding templates into GCP's original magic-modules. We put all azure-specific code in azure folders, and only inject the least amount of code into original files.

We also support running magic-modules side-by-side, by using the --cloud switch. By default we will use GCP templates and logic, so it will not affect any existing magic-modules user code.

magodo and others added 30 commits December 3, 2019 14:05
add subcategory header to document template
…ucture

Search example consider foder struct by autorest.cli
don't set Default for output-only property
when searching folder form example, considering suffix of "-preview"
disable the comment at header
Confrom new tf provider style
follow new client get scheme for datasource
put generated files to internal/services/<rp> folder
Testcase Impl. Change & Package name Change (according to provider refactor)
add default timeout for d/r
resource group name case sensitive
remove `sidebar_current` from gen doc
Terraform azure provider currently introduce custom parseID function,
which is to replace previous `azure.ParseAzureResourceID()`.

Furthermore, this is used at `Importer` to validate importing ID and
in acctest.
Support custom parseID function
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.

6 participants