Skip to content
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 support for collections in all namespaces #872

Open
lcarva opened this issue Jan 22, 2024 · 0 comments
Open

Add support for collections in all namespaces #872

lcarva opened this issue Jan 22, 2024 · 0 comments

Comments

@lcarva
Copy link
Member

lcarva commented Jan 22, 2024

Today, collections are widely used in the policies under the release namespace. The docs know how to display them. This is nice.

This issue is about adding the same level of support for all namespaces (or at a bare minimum to the task namespace.) If we try to do that today, the website fails to build with an obscure error:

[15:46:50.902] FATAL (antora): Cannot read properties of undefined (reading 'title')

This seems to originate from here.

Acceptance Criteria

  • When using collections in the policy rules from the task namespace, the website build does not break and they are properly described in the website.
  • Revert Remove collections from step image registries #873
  • As a stretch goal, make this true for all namespaces.
lcarva added a commit to lcarva/ec-policies that referenced this issue Jan 22, 2024
Collections are not properly supported in the `task` namespace, see
enterprise-contract#872

Signed-off-by: Luiz Carvalho <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant