-
Notifications
You must be signed in to change notification settings - Fork 452
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
only use vApp properties that are UserConfigurable #751
Conversation
Signed-off-by: Adam Robinson <adarobin@umich.edu>
Thanks @adarobin. This looks really great. Would it be possible to get an error thrown when a configuration attempts to set a non user configurable property? That way there won't be any confusion on why properties are being ignored. |
@bill-rich Not opposed to adding a message, but I'm not sure how to handle that. If you look at #394, properties that are not user configurable are getting pulled in regardless of if they are actually in the Terraform code or not. For example, if I attempt to deploy a Nested ESXi OVA without this patch the deployment will fail as the vApp contains the property I worked around this by ignoring all properties with |
@bill-rich My brain isn't fully working on a Monday. It looks like the existing error handling that is right after this change is already taking care of this. If I try setting
|
Just pushed code that should do what you are asking. This is what I see if I specify
|
@bill-rich thoughts on the latest code? |
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 adding in the error message. This looks ready to merge!
This PR resolves #394 by ignoring vApp attributes that have
UserConfigurable
set toFalse
.