Add a new devfile version with an https endpoint

[vinokurig]

What does this PR do?:

Add an https endpoint to be able to run the application on Eclipse CHE

Which issue(s) this PR fixes:

eclipse-che/che#22869

PR acceptance criteria:

• Contributing guide
  Have you read the devfile registry contributing guide and followed its instructions?
• Test automation
  Does this repository's tests pass with your changes?
• Documentation
  Does any documentation need to be updated with your changes?
• Check Tools Provider
  Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)

How to test changes / Special notes to the reviewer:

[openshift-ci]

Hi @vinokurig. Thanks for your PR.

I'm waiting for a devfile 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.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[thepetk]

Following our updates for #312 & #298 I'm not sure if we should add an extra version or update the latest to be 2.2.1.

More detailed for this case, I'm not sure if we should follow the proposed solution or update the 2.2.0 to be 2.2.1 (dir names, version numbers and the stack.yaml).

cc @michael-valdron @Jdubrick

[Jdubrick]

Following our updates for #312 & #298 I'm not sure if we should add an extra version or update the latest to be 2.2.1.

More detailed for this case, I'm not sure if we should follow the proposed solution or update the 2.2.0 to be 2.2.1 (dir names, version numbers and the stack.yaml).

cc @michael-valdron @Jdubrick

Based on the prior chores to update .net to https I think my vote is that we should update 2.2.0 to use https instead of a creating a new version to maintain consistency in our changes, especially if that is all that is being changed.

[vinokurig]

@thepetk @Jdubrick I reverted the latest commit and made the change to the existed 2.2.0 version

[thepetk]

@thepetk @Jdubrick I reverted the latest commit and made the change to the existed 2.2.0 version

@vinokurig apologies our discussion here might be misleading. I think it would be nice to patch the 2.2.0 version after the fix you've added. I think the best way to go is:

• Move the 2.2.0 version dir to 2.2.1 version dir.
• Replace the 2.2.0 with the 2.2.1 version in the stack.yaml
• Inside the devfile.yaml of the 2.2.1 version update the metadata.version field to be 2.2.1.

This way we only have the 2.2.1 version visible.

[vinokurig]

@thepetk

@vinokurig apologies our discussion here might be misleading. I think it would be nice to patch the 2.2.0 version after the >fix you've added. I think the best way to go is:

Move the 2.2.0 version dir to 2.2.1 version dir.
Replace the 2.2.0 with the 2.2.1 version in the stack.yaml
Inside the devfile.yaml of the 2.2.1 version update the metadata.version field to be 2.2.1.
This way we only have the 2.2.1 version visible.

Done, please take a look.

[thepetk]

@vinokurig I've only added a minor suggestion

[vinokurig]

@thepetk Looks like all comments are addressed, could you please take a look?

[thepetk]

@thepetk Looks like all comments are addressed, could you please take a look?

@vinokurig I think only the DCO check needs to be fixed. Overall looks good to me.

/ok-to-test

[thepetk]

@thepetk Looks like all comments are addressed, could you please take a look?

@vinokurig I think only the DCO check needs to be fixed. Overall looks good to me.

/ok-to-test

@vinokurig minor suggestion is to remove the 2.2.0 version directory as it is no longer listed in the stack.yaml file

[vinokurig]

@thepetk

@vinokurig minor suggestion is to remove the 2.2.0 version directory as it is no longer listed in the stack.yaml file

Done.

[thepetk]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: thepetk, vinokurig

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• stacks/OWNERS [thepetk]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vinokurig]

@thepetk I don't have merge permissions, could you merge please?