-
Notifications
You must be signed in to change notification settings - Fork 508
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
Add a new object that extends KubernetesObject to generically handle all objects that have a spec
property
#1221
Add a new object that extends KubernetesObject to generically handle all objects that have a spec
property
#1221
Conversation
Welcome @bencooper222! |
@bencooper222 thanks for the PR. While most Kubernetes resources do have a Spec field, there are a number of others (ConfigMap is probably the most obvious example) which do not. I think we could introduce a |
0a360eb
to
89b3cc3
Compare
Thank you for the quick response! I've revised the PR to match your suggestion. |
spec
property
.npmrc
Outdated
@@ -0,0 +1,2 @@ | |||
# for contributors with a corporate registry, this will make sure we use the public one |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove this file as it is unrelated to this change.
@bencooper222 looks good, but please remove the |
773cb7b
to
89b3cc3
Compare
89b3cc3
to
c0c24dc
Compare
Fixed |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bencooper222, brendandburns 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:
Approvers can indicate their approval by writing |
Adding an interface for an object with a spec property which most, but not all Kubernetes objects have.
Fixes #1218