This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
Fix "vpcIdRef" field in EC2 and Route53 subresources #154
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
Signed-off-by: ezgidemirel <ezgidemirel91@gmail.com>
|
/backport release-0.4 |
|
Successfully created backport PR #156 for |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Signed-off-by: ezgidemirel ezgidemirel91@gmail.com
Description of your changes
This PR replaces "vpcidRef" fields with "vpcIdRef" in EC2 and Route53 subresources. In addition to that, it refactors reference addition in some of the resources. Instead of creating a new map and assign it to references, we should append new keys during resource configurations.
Fixes #153
I have:
make reviewable testto ensure this PR is ready for review.How has this code been tested
I applied example manifests of VPC and Subnet resources.