-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
AKS: Add-On Profiles #1751
Merged
Merged
AKS: Add-On Profiles #1751
Changes from 41 commits
Commits
Show all changes
42 commits
Select commit
Hold shift + click to select a range
5865322
Added kubernetes_cluster advanced network creation
lfshr 305c1d0
Changed network_profile from TypeSet to TypeList
lfshr df237b2
Added kubernetes_cluster advanced network creation
lfshr e3ec37e
Changed network_profile from TypeSet to TypeList
lfshr a3ff5b0
Merge branch 'containerservices-advancednetworking' of https://github…
lfshr b7d274b
Updated ForceNew attributes on kubernetes_cluster.network_profile params
lfshr 11bed67
Added advanced network read functionality
lfshr 30f39ff
Added tests for kubernetes_cluster.network_profile
lfshr 195e7d6
Fixed indentations
lfshr f8f5626
Fixed function name in tests
lfshr 25c6e6e
Fixed property name in test
lfshr 48cff90
Fixed variable name
lfshr 2dd887c
working on data source for kubernetes cluster
lfshr 1bdf8b6
Merge branch 'containerservices-advancednetworking' of https://github…
lfshr 33c84c6
Fixed issue with datasource not working
lfshr f9786e1
Added network_policy and fixed read
lfshr 02b22e5
Removed network_policy as unsupported
lfshr b62a643
Added example of advanced networking
lfshr 377c52f
Added test for data_source
lfshr 7453f41
Made address space more sensible
lfshr c90ea55
Removing kubenet test.
lfshr 16e7d3e
Made network_plugin a mandatory field.
lfshr 675d0b9
Updated documentation to include network_profile
lfshr 7c21183
Fixing the build
tombuildsstuff 1959c2f
Added ForceNew to network_profile
lfshr 518cacc
Made the docs a little clearer
lfshr 9faeb69
Documenting a required field
tombuildsstuff 1ef6ccf
Rephrasing the data sources
tombuildsstuff dac7913
Making the `network_profile` block computed
tombuildsstuff 48d5ed7
Fixing the field we're asserting on
tombuildsstuff a54aa89
Conditionally expanding the network_profile block.
tombuildsstuff 9e862eb
Validation to ensure that a Subnet ID is assigned to the cluster when…
tombuildsstuff f2219c5
Updating the documentation to mention the new behaviour
tombuildsstuff 8a23d24
Adding independent tests for Kubenet and Azure networking profiles
tombuildsstuff 8d08c53
Conditional validation of the `docker_bridge_cidr`, `dns_service_ip` …
tombuildsstuff a72f105
Updating the docs
tombuildsstuff ff3e206
Fixing the tests
tombuildsstuff 7d62f51
Merge branch 'master' into containerservices-advancednetworking
tombuildsstuff 403bc1d
Adding back in the changes from PR #1502 since they were lost in the …
tombuildsstuff be893dc
Renaming the methods to `addonProfiles` to match the sdk
tombuildsstuff 018a6db
fixing the quotes
tombuildsstuff 3106ee1
Merge branch 'master' into containerservices-advancednetworking
tombuildsstuff File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't we just rename either this function or
flattenAzureRmKubernetesClusterAddonProfiles
and reuse it? It's exactly the same function with the same interface, just a different name.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably - but historically this has caused us issues where the schema's diverged - so we're trying to avoid that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I follow, how could it diverge if the output is coming from the exact same API call? If the API response is going to diverge, then both functions (as they're exactly the same except name) need fixing, AFAICT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the schema being the Terraform schema here - since one is a Data Source and hence Computed (this one) vs the other being a Resource / not computed. We've had PR's in the past with folks adding items to each independently, which means there's a Set error when this happens - as such it appears preferable to dupe this logic?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, I see what do you mean 🤔That's tricky, yeah.
I wish we had a better way to reuse parts of schema between resources and data sources 😞
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this discussion -- this is something we can run into on AWS as well since we generally are pushing for separate schema definitions and read functions, but usually sharing the flatten functions. 🤔