-
Notifications
You must be signed in to change notification settings - Fork 89
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
Update new provider documentation #115
Conversation
Signed-off-by: Muvaffak Onus <[email protected]>
Signed-off-by: Muvaffak Onus <[email protected]>
e11c681
to
785f496
Compare
083771d
to
ca4949a
Compare
Signed-off-by: Muvaffak Onus <[email protected]>
ca4949a
to
2a20f45
Compare
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.
Thanks @muvaf, lgtm. Left some comments for you to consider.
) | ||
|
||
func GetProvider() *tjconfig.Provider { | ||
... | ||
for _, configure := range []func(provider *tjconfig.Provider){ | ||
// add custom config functions | ||
- null.Configure, |
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.
nit: Why do we have the literal null
here?
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.
It's because the provider name is null
, i.e. hashicorp/null
.
// This resource need the repository in which branch would be created | ||
// as an input. And by defining it as a reference to Repository | ||
// object, we can build cross resource referencing. See | ||
// repositoryRef in the example in the Testing section below. | ||
r.References["repository"] = config.Reference{ | ||
Type: "github.com/crossplane-contrib/provider-jet-github/apis/repository/v1alpha1.Repository", | ||
Type: "github.com/myorg/provider-github/apis/repository/v1alpha1.Repository", |
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.
Looking at the examples below, should myorg
be upbound
or vice versa?
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.
It should be myorg
everywhere in the user's provider since they'll need to use their own organization. Is there an inconsistency you caught?
Signed-off-by: Muvaffak Onus <[email protected]>
Signed-off-by: Muvaffak Onus <[email protected]>
Description of your changes
Updates to work with Upjet.
Fixes #114
I have:
make reviewable
to ensure this PR is ready for review.backport release-x.y
labels to auto-backport this PR if necessary.How has this code been tested
Together with crossplane/upjet-provider-template#7 and confirmed that I see repo and branch.