-
Notifications
You must be signed in to change notification settings - Fork 900
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 specification for Composition Functions #4640
Conversation
This is a first pass at a 'formal' spec for a Composition Function. I think it will be important for all Functions to behave in a similar way in order for us to build tooling around them. Relates to https://github.com/crossplane/crossplane/issues/3714 Signed-off-by: Nic Cope <nicc@rk0n.org>
Signed-off-by: Nic Cope <nicc@rk0n.org>
Signed-off-by: Nic Cope <nicc@rk0n.org>
Signed-off-by: Nic Cope <nicc@rk0n.org>
@plumbis Added you as optional to review this for readability. |
A Function MUST NOT assume it is deployed in any particular way, for example | ||
that it is running as a Kubernetes Pod in the same cluster as Crossplane. | ||
|
||
A Function SHOULD fail gracefully if it does not have network access, for |
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.
A Function SHOULD fail gracefully if it does not have network access, for | |
A Function SHOULD fail gracefully if it needs but does not have network access, for |
I assume this is not relevant for an offline function.
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.
LGTM - now I just need to get started on that Python SDK
A Function MUST listen for gRPC requests on TCP port 9443, regardless of whether | ||
they are using mTLS transport security or have transport security disabled. | ||
|
||
A Function MUST not disable gRPC transport security unless the `--insecure` flag |
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.
MUST NOT
Description of your changes
Relates to crossplane/docs#579
This is a first pass at a 'formal' spec for a Composition Function. I think it will be important for all Functions to behave in a similar way in order for us to build tooling around them.
I have:
Runmake reviewable
to ensure this PR is ready for review.Addedbackport release-x.y
labels to auto-backport this PR, if necessary.Opened a PR updating the docs, if necessary.