You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On running the kustomize build . in the directory results in an error.
Error: accumulating resources: accumulation err='accumulating resources from 'https://github.com/novuhq/novu.git//docker/kubernetes/kustomize?ref=086b62851098d59809cfcc1773a91dc3aed1eec6': URL is a git repository': failed to run '/usr/bin/git submodule update --init --recursive': Submodule 'enterprise' ([email protected]:novuhq/packages-enterprise.git) registered for path '.source'
Cloning into '/private/var/folders/0z/07y73hp94xl_bjfrsfctztcc0000gn/T/kustomize-347933844/.source'...
ERROR: Repository not found.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
fatal: clone of '[email protected]:novuhq/packages-enterprise.git' into submodule path '/private/var/folders/0z/07y73hp94xl_bjfrsfctztcc0000gn/T/kustomize-347933844/.source' failed
Failed to clone '.source'. Retry scheduled
Cloning into '/private/var/folders/0z/07y73hp94xl_bjfrsfctztcc0000gn/T/kustomize-347933844/.source'...
ERROR: Repository not found.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
fatal: clone of '[email protected]:novuhq/packages-enterprise.git' into submodule path '/private/var/folders/0z/07y73hp94xl_bjfrsfctztcc0000gn/T/kustomize-347933844/.source' failed
Failed to clone '.source' a second time, aborting
: exit status 1
👟 Reproduction steps
Copy the URL of the docker/kubernetes/kustomize directory as resource in kustomization.yaml file.
It should clone the files locally without getting the submodule and build the files in docker/kubernetes/kustomize directory.
👎 Actual Behavior with Screenshots
Here is the error:
Error: accumulating resources: accumulation err='accumulating resources from 'https://github.com/novuhq/novu.git//docker/kubernetes/kustomize?ref=086b62851098d59809cfcc1773a91dc3aed1eec6': URL is a git repository': failed to run '/usr/bin/git submodule update --init --recursive': Submodule 'enterprise' ([email protected]:novuhq/packages-enterprise.git) registered for path '.source'
Cloning into '/private/var/folders/0z/07y73hp94xl_bjfrsfctztcc0000gn/T/kustomize-347933844/.source'...
ERROR: Repository not found.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
fatal: clone of '[email protected]:novuhq/packages-enterprise.git' into submodule path '/private/var/folders/0z/07y73hp94xl_bjfrsfctztcc0000gn/T/kustomize-347933844/.source' failed
Failed to clone '.source'. Retry scheduled
Cloning into '/private/var/folders/0z/07y73hp94xl_bjfrsfctztcc0000gn/T/kustomize-347933844/.source'...
ERROR: Repository not found.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
fatal: clone of '[email protected]:novuhq/packages-enterprise.git' into submodule path '/private/var/folders/0z/07y73hp94xl_bjfrsfctztcc0000gn/T/kustomize-347933844/.source' failed
Failed to clone '.source' a second time, aborting
: exit status 1
Novu version
next
npm version
8.12.1
node version
v18.4.0
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
📜 Description
Hello,
I was trying to directly enter the link to the
docker/kubernetes/kustomize
in mykustomization.yaml
file as mentioned below:On running the
kustomize build .
in the directory results in an error.👟 Reproduction steps
docker/kubernetes/kustomize
directory as resource inkustomization.yaml
file.kustomize build .
kustomization.yaml
👍 Expected behavior
It should clone the files locally without getting the submodule and build the files in
docker/kubernetes/kustomize
directory.👎 Actual Behavior with Screenshots
Here is the error:
Novu version
next
npm version
8.12.1
node version
v18.4.0
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Contributing Guidelines?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: