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(cli): import constructs for all API levels #379

Merged
merged 8 commits into from
Nov 17, 2020
Merged

Conversation

eladb
Copy link
Contributor

@eladb eladb commented Nov 16, 2020

Following this change, when using cdk8s import to generate constructs from schemas, the CLI will generate constructs for all API levels and not just the latest stable version.

The name of the generated class will now include the API level, unless this is a v1 resource. For example, v1/Pod will be called Pod, while v1beta1/Ingress will be called IngressV1Beta1.

This change only applies to cdk8s import k8s and does not apply when importing CRDs, in which case a single CRD always includes a single resource definition.

BREAKING CHANGE: when importing k8s api objects using cdk8s import, non-stable APIs will be have an API level postfix. For example, [email protected] will have an IngressV1Beta1 API object.

  • cli: The --include CLI option has been removed since all API objects are always imported.

Resolves #380


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Following this change, when using `cdk8s import` to generate constructs from schemas, the CLI will generate constructs for all API levels and not just the latest stable version.

The name of the generated class will now include the API level, unless this is a `v1` resource. For example, `v1/Pod` will be called `Pod`, while `v1beta1/Ingress` will be called `IngressV1Beta1`.

This change only applies to `cdk8s import k8s` and does not apply when importing CRDs, in which case a single CRD always includes a single resource definition.

BREAKING CHANGE: when importing k8s api objects using `cdk8s import`, non-stable APIs will be have an API level postfix. For example, [email protected] will have an `IngressV1Beta1` API object.
@eladb eladb requested a review from iliapolo November 16, 2020 20:47
Copy link
Member

@iliapolo iliapolo left a comment

Choose a reason for hiding this comment

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

Also need to re-import cdk8s+

packages/cdk8s-cli/src/cli/cmds/import.ts Show resolved Hide resolved
@mergify
Copy link
Contributor

mergify bot commented Nov 17, 2020

Your pull request will be updated and merged automatically (do not update manually).

@mergify mergify bot merged commit b0d7621 into master Nov 17, 2020
@mergify mergify bot deleted the benisrae/api-levels branch November 17, 2020 12:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Annotate non-stable API levels in imported k8s resources
2 participants