-
Notifications
You must be signed in to change notification settings - Fork 37
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
A .manifest
file is not recognized as a project root by the new file templating
#1077
Labels
Comments
anderseknert
added a commit
that referenced
this issue
Sep 9, 2024
We previously traversed the path downwards, so if we had `foo/bar/.manifest` and `foo/bar/baz` was provided, we would not find `foo/bar` as a root. Now search for manifests from the root. Fixes #1077 Signed-off-by: Anders Eknert <anders@styra.com>
anderseknert
added a commit
that referenced
this issue
Sep 9, 2024
We previously traversed the path downwards, so if we had `foo/bar/.manifest` and `foo/bar/baz` was provided, we would not find `foo/bar` as a root. Now search for manifests from the root. Fixes #1077 Signed-off-by: Anders Eknert <anders@styra.com>
anderseknert
added a commit
that referenced
this issue
Sep 9, 2024
We previously traversed the path downwards, so if we had `foo/bar/.manifest` and `foo/bar/baz` was provided, we would not find `foo/bar` as a root. Now search for manifests from the root. Fixes #1077 Signed-off-by: Anders Eknert <anders@styra.com>
anderseknert
added a commit
that referenced
this issue
Sep 9, 2024
We previously traversed the path downwards, so if we had `foo/bar/.manifest` and `foo/bar/baz` was provided, we would not find `foo/bar` as a root. Now search for manifests from the root. Fixes #1077 Signed-off-by: Anders Eknert <anders@styra.com>
anderseknert
added a commit
that referenced
this issue
Sep 9, 2024
We previously traversed the path downwards, so if we had `foo/bar/.manifest` and `foo/bar/baz` was provided, we would not find `foo/bar` as a root. Now search for manifests from the root. Fixes #1077 Signed-off-by: Anders Eknert <anders@styra.com>
charlieegan3
pushed a commit
that referenced
this issue
Sep 9, 2024
We previously traversed the path downwards, so if we had `foo/bar/.manifest` and `foo/bar/baz` was provided, we would not find `foo/bar` as a root. Now search for manifests from the root. Fixes #1077 Signed-off-by: Anders Eknert <anders@styra.com>
srenatus
pushed a commit
to srenatus/regal
that referenced
this issue
Oct 1, 2024
We previously traversed the path downwards, so if we had `foo/bar/.manifest` and `foo/bar/baz` was provided, we would not find `foo/bar` as a root. Now search for manifests from the root. Fixes StyraInc#1077 Signed-off-by: Anders Eknert <anders@styra.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given a directory like:
I would expect the templating of a new file under the
bundle
directory to usebundle
as a root, and a new file (foo/bar/policy.rego
) to havepackage foo.bar
. Instead, the workspace root is used, and package ends up asbundle.foo.bar
The text was updated successfully, but these errors were encountered: