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

🐛 OCI artifact name error causing prompt to be re-appended #230

Open
arturshadnik opened this issue Sep 16, 2024 · 1 comment
Open

🐛 OCI artifact name error causing prompt to be re-appended #230

arturshadnik opened this issue Sep 16, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@arturshadnik
Copy link
Member

arturshadnik commented Sep 16, 2024

Description

When configuring OCI rules, if there is an error in the artifact name, it will cause part of the prompt to be re-appended, which makes the prompts grow longer.

With each error, (newline separated values) is added onto the prompt again.

Reproduction steps

1. Perform either a `validator rules check` or `validator install` => `validator rules apply...`
2. "Yes" when prompted to configure OCI rules
3. Fill in required details until the step where you are prompted to enter artifact names.
4. Enter any artifact name that does not match the expected regex `^<registry_host>/.*$`
5. Observe the prompt now has the phrase `(newline separated values)` repeated twice. 
6. Perform steps 4-5 as many times as desired, each time observing the prompt getting longer.

Environment

validatorctl: v0.2.1
validator-plugin-oci: v0.3.3

Screenshots

image

Logs

No response

@arturshadnik arturshadnik added the bug Something isn't working label Sep 16, 2024
Copy link

dosubot bot commented Dec 16, 2024

Hi, @arturshadnik. I'm Dosu, and I'm helping the validatorctl team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • Bug in OCI artifact name configuration.
  • Error message appends "(newline separated values)" repeatedly.
  • Occurs when artifact name doesn't match expected regex pattern.
  • Reported in validatorctl v0.2.1 and validator-plugin-oci v0.3.3.
  • No comments or additional activity since the issue was opened.

Next Steps:

  • Is this issue still relevant to the latest version of the validatorctl repository? If so, please comment to keep the discussion open.
  • If there is no further activity, the issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Dec 16, 2024
@TylerGillson TylerGillson removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants