Skip to content
This repository has been archived by the owner on Oct 24, 2023. It is now read-only.

feat: Support dynamic AzureEnvironmentSpecConfig #386

Merged
merged 14 commits into from
Feb 12, 2019

Conversation

honcao
Copy link
Member

@honcao honcao commented Jan 25, 2019

Reason for Change:

Feature Change for #278

Issue Fixed:

Fix #278

Requirements:

Notes:

@codecov
Copy link

codecov bot commented Jan 25, 2019

Codecov Report

Merging #386 into master will decrease coverage by 0.09%.
The diff coverage is 98.39%.

@@            Coverage Diff            @@
##           master     #386     +/-   ##
=========================================
- Coverage   53.42%   53.33%   -0.1%     
=========================================
  Files          95       98      +3     
  Lines       14361    16769   +2408     
=========================================
+ Hits         7673     8943   +1270     
- Misses       6025     7047   +1022     
- Partials      663      779    +116

@honcao
Copy link
Member Author

honcao commented Jan 25, 2019

/assign @jackfrancis

@honcao
Copy link
Member Author

honcao commented Jan 28, 2019

@jackfrancis Thanks to review the code. I resolve the your comments and E2E test are passed now with the latest code.

@jackfrancis
Copy link
Member

@honcao I understand why we need to define new types for these configurations in the vlabs type spec, as we're now going to be accepting them as configurable input. I don't understand why we need to copy over all the default values, however, as we can re-use the existing defaults flow that happens after the vlabs type has been converted to the superset api type, right?

Am I missing something?

@honcao
Copy link
Member Author

honcao commented Jan 30, 2019

@jackfrancis , you are correct, we do not need all the defaults in azenvtypes.go, only AzureStackCloudSpec is required. I will update the code.

@honcao
Copy link
Member Author

honcao commented Feb 6, 2019

@jackfrancis thanks.
Could we merge the PR as-is now? It will unblock me to send PR to support dynamic location.

And I will follow up with team to collect thoughts and refractor the code later?

@tariq1890 tariq1890 changed the title feat:Support dynamic AzureEnvironmentSpecConfig feat: Support dynamic AzureEnvironmentSpecConfig Feb 12, 2019
Copy link
Contributor

@tariq1890 tariq1890 left a comment

Choose a reason for hiding this comment

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

LGTM

@mboersma
Copy link
Member

/lgtm

@acs-bot
Copy link

acs-bot commented Feb 12, 2019

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: honcao, mboersma

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mboersma mboersma merged commit 7975ccb into Azure:master Feb 12, 2019
@honcao honcao deleted the environmentspec branch March 4, 2019 15:17
juhacket pushed a commit to juhacket/aks-engine that referenced this pull request Mar 14, 2019
* Support dynamic AzureEnvironmentSpecConfig

* remove the DcosSpecConfig from surface area

* use !="" to compare string for readability

* remove unused default AzureEnvironmentSpecConfig in vlabs

* Update pkg/api/azenvtypes.go for AzureStackCloudSpec comments

Co-Authored-By: honcao <honcao@microsoft.com>

* put default value of Azure Stack Environment Spec Config into default.go

* add an wapper assging the dst string if the src string is not empty

* assigning structs to variables for reuse

* add new pubic function to support azurestack.

* update comments for GetDefaultStringWithOverwrite

* move set default custom cloud profile to seperate file
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support dynamic AzureEnvironmentSpecConfig
6 participants