Is generating-a-provider doc up do date?

[IvanTurgenev1]

What problem are you facing?

The example has the following block of code :

pc := tjconfig.NewProviderWithSchema([]byte(providerSchema), resourcePrefix, modulePath,
    tjconfig.WithIncludeList([]string{
        "github_repository$",
        "github_branch$",
    }))

but in upjet template this code looks really different

	pc := tjconfig.NewProvider([]byte(providerSchema), resourcePrefix, modulePath, nil,
		tjconfig.WithIncludeList(ExternalNameConfigured()),
		tjconfig.WithDefaultResourceOptions(
			ExternalNameConfigurations(),
		))

is this doc need to be updated? or i did smth wrong?

[IvanTurgenev1]

Looks like doc is outdated:
Problems arise when generating a provider.
after using hack.sh I get access errors to repositories, cause they are simple doesn't exist ><

github.com/upbound/provider-salt/cmd/provider imports
github.com/upbound/upjet-provider-salt/apis/v1alpha1: cannot find module providing package github.com/upbound/upjet-provider-salt/apis/v1alpha1: module github.com/upbound/upjet-provider-salt/ apis/v1alpha1: git ls-remote -q origin in /Users/ivan.turgenev/git/upjet-provider-salt/.work/pkg/pkg/mod/cache/vcs/baf673e8d21bf52024ae6fc58c550a41252213a41280b819a69d967976c582: exit
ERROR: Repository not found.

[muvaf]

Thanks for opening this issue @IvanTurgenev1 ! Yes, it seems it's outdated. I'll work on updating it and get back to you.

[muvaf]

@IvanTurgenev1 The PR #115 contains most up-to-date information including the TF provider documentation parsing for CRD API references!