Add support for setting the public IP SkU #187
Merged
Conversation
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
|
@simonjefford This looks good. Can you add something to the readme. We're looking to move that content to the website in the near future and I want to make sure we don't miss this. |
Signed-off-by: Simon Jefford <simon.jefford@fourth.com>
|
@tas50 that's done - thanks for taking a look |
|
Thanks @simonjefford. I'll get this shipped now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
I currently have a need to stand up test kitchen instances in a network with a Nat Gateway in order to get known outbound IP addresses for whitelisting purposes - we don't have ExpressRoute or Private Link set up on this network. In order to do this, public IP resources must have a SKU of "Standard" rather than "Basic". This PR allows this SKU to be set in kitchen.yml.
Issues Resolved
N/A
Check List