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
Updating default_system_registry behavior at rancher2_app_v2 resource #1265
Conversation
Hi, I need reviews on this PR however, I don't have permission to add reviewers. Also, there is a failing automated test but it has nothing to do with PR code changes and I can't restart the drone build, how should I proceed? |
Hey @nicholasSUSE - I've added Andy, Sergey, and Bruno - whichever two get to take a look first. |
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'd update the tf docs cluster_v2.md
to reflect the new functionality of system_default_registry
now and make sure to test it having an empty value/not being set which would cause tf to use the global system registry within Rancher and make sure that still works. Lgtm
Thank you for your review. |
98b12ac
to
0f6f81f
Compare
0f6f81f
to
07a251d
Compare
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.
Commented
f9b1612
to
41a1a53
Compare
I have tested both scenarios: Setting the system_default_registry variable
And not setting. The This way, whatever override we do with the new variable behavior will output the right value. |
41a1a53
to
871a5fd
Compare
Issue:
#1187
Problem
The terraform resource
rancher2_app_v2
had no Argument for setting up a Custom System Registry, limiting clients to install an app only from a previously configured SystemDefaultRegistry.There was in place a computed attribute named
default_system_registry
.Solution
Transform the computed attribute
default_system_registry
into an optional argument for the resource too.Testing
The reproducing steps in the Github Issue are very hard and take a long time to execute.
In order to test without needing to set all the infrastructure (specially the private registry with all the images):
Testing With Terraform:
rancher2_app_v2
to create a new app installation passing the recently createdsystem_default_registry
argument pointing to a random string pretending to be the private registry DNS.Results when trying to install CIS Benchmark passing a random string as the value:
Engineering Testing
Manual Testing
Part of the terraform code to execute the tests:
Automated Testing
QA Testing Considerations
Regressions Considerations