Skip to content
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

feat: add vapp properties #299

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

feat: add vapp properties #299

wants to merge 2 commits into from

Conversation

MrKeiKun
Copy link

@MrKeiKun MrKeiKun commented Aug 5, 2023

No description provided.

@MrKeiKun MrKeiKun requested a review from a team as a code owner August 5, 2023 13:27
@hashicorp-cla
Copy link

hashicorp-cla commented Aug 5, 2023

CLA assistant check
All committers have signed the CLA.

@harlequin
Copy link

harlequin commented Sep 11, 2023

Please merge, feature would be useful

@JenGoldstrich Can you review?

@tenthirtyam
Copy link
Collaborator

@MrKeiKun Couls to please provide A summary and test results in the pull request description?

@tenthirtyam tenthirtyam changed the title Added vApp Properties feat: add vapp properties Oct 13, 2023
@tenthirtyam tenthirtyam linked an issue Oct 13, 2023 that may be closed by this pull request
@tenthirtyam
Copy link
Collaborator

CI is failing.

Copy link
Contributor

@lbajolet-hashicorp lbajolet-hashicorp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @MrKeiKun,

The initial draft looks OK to me, I left a fix suggestion for the generation problem, I believe that if you change the type to be a public structure, it should mend the generated code.

That being said, I'm not sure we need to introduce an extra structure to the package, it seems the only attribute could be directly part of the general config, especially since we don't define any function on the structure itself.
On another note, I am very much unfamiliar with VSphere so please bear with me here, but are there other kind of configs we want to support regarding the VAppConfig? I'm also a bit cautious regarding the properties type, since it's a map of string->string, this implies that all attributes' value must be a string, and from the screenshot I saw, there seems to be multiple possibilities, is that right? I see on the issue someone trying to input some XML, is there a standard format to specify that, with type information? If so we should probably aim to support this also (though this can be for later I presume).

builder/vsphere/iso/step_create.go Show resolved Hide resolved
@tenthirtyam tenthirtyam marked this pull request as draft October 19, 2023 19:10
@tenthirtyam
Copy link
Collaborator

✅ CI is now Successful.
✅ Marking as Ready for Review.

@tenthirtyam tenthirtyam marked this pull request as ready for review November 8, 2023 18:13
Copy link
Member

@nywilken nywilken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look good to me as well. But as Lucas mentioned there is room for improvement when it comes to the vAppConfig type. It also appears that since this is in both iso and clone builders things can be brought into common. But we can leave that for a separate PR.

@tenthirtyam thanks for pushing forward and testing. I will approve the PR as is and wait to hear back on the docs before merging.

@tenthirtyam tenthirtyam marked this pull request as draft November 10, 2023 15:32
@tenthirtyam
Copy link
Collaborator

Marking this as draft for further review and outcome testing before merging.

@tenthirtyam tenthirtyam added the stage/needs-verification Issue needs verifying it still exists label Nov 10, 2023
@harlequin
Copy link

Any Updates to this?

@adeturner
Copy link

Agree, I've still got the issue in #305. Would be good to get this merged even in a "beta state". Currently with OVF templates the only work around is to use ssh/remote-exec provisioners which are marked by hashicorp "last resort."

@harlequin
Copy link

harlequin commented Feb 13, 2024

@adeturner Can you please provide some examples for your ssh/remote exec to this issue?
I guess this "last resort" solution will help many people until it's implemented ...

@adeturner
Copy link

@harlequin no worries, see remote_exec_workaround and the_vapp_ideal

@tenthirtyam tenthirtyam added this to the v1.2.6 milestone Mar 7, 2024
@tenthirtyam
Copy link
Collaborator

Thus far, I've not been able to perform a build that will apply these properties to an image with the vsphere-iso builder after building from the source/branch.

@MrKeiKun 👋 - could you please provide a summary, minimal configuration example, test results in the pull request description?

Without this information I am reticent to move this one forward until the this can be successfully tested.

@tenthirtyam tenthirtyam added this to the Backlog milestone Apr 9, 2024
@tenthirtyam tenthirtyam self-assigned this Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
builder/vsphere-iso Builder: vsphere-iso enhancement stage/needs-verification Issue needs verifying it still exists
Projects
None yet
Development

Successfully merging this pull request may close these issues.

vsphere-iso: Add support for vApp properties
8 participants