[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [che-dev] Incompatible change in devfile format
|
That's not a silly question at all. We are technically in beta and we don't support older versions of the spec. That explains why we are not incrementing it yet. But for the GA we should probably think about bumping the version to 1.0.0.
Hi,
This might be a silly question, but whi is apiVersion not being
incremented with each of these incompatible changes?
Thanks,
Dave.
On 07/06/2019 12:09, Lukas Krejci wrote:
> Hi all,
>
> This change affects ALL existing devfiles but we hope it is for the better.
>
> In order to align the devfile format with Kubernetes conventions more
> (and to open the door for devfile possibly becoming a CRD in the
> future), we're making the following simple yet important changes:
>
> * 'specVersion' attribute is being renamed to 'apiVersion'
> * 'name' attribute is being moved under a new 'metadata' key
>
> So the old devfile starting with the usual snippet:
>
> specVersion: 0.0.1
> name: acme-devfile
> ...
>
> will have to change to:
>
> apiVersion: 0.0.1
> metadata:
> name: acme-devfile
> ...
>
>
> This change is slated for the next milestone of Che 7 and you can track
> the progress in the PR https://github.com/eclipse/che/pull/13490.
>
> Hope it doesn't cause too much trouble for you.
>
> With regards,
>
> Lukas Krejci
>
> _______________________________________________
> che-dev mailing list
> che-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/che-dev
--
Dave Neary - Eclipse Che Ecosystem & Community Manager
Open Source and Standards - Red Hat
E: dneary@xxxxxxxxxx / T: @nearyd / Ph: +1-978-799-3338
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev
