Hi @itsCheithanya. Thanks for your PR.

I'm waiting for a coreos member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

I think there are more options to look at to force the platform being used.

Looks like this also needs code formatting.

Please use a more descriptive commit message that notably includes at the end:

Fixes: https://github.com/coreos/coreos-assembler/issues/3509

I think there are more options to look at to force the platform being used.

Looks like this also needs code formatting.

Yes i will add for all of them ,just wanted to know if I'm in the right direction

Please use a more descriptive commit message that notably includes at the end:

Fixes: https://github.com/coreos/coreos-assembler/issues/3509

Sorry i just made this PR for code clarifications not an actual issue solving one, will make sure to follow it for the coming PR's

Yes i will add for all of them ,just wanted to know if I'm in the right direction

Yes, looks like you're going in the right direction.

@travier
#87c8ea4
Made the required code changes for all other platform options ,Let me know if anything needs to be done

@travier As part of the backlog refinement, we came across this issue. We wanted to know if this is a relevant issue.