Skip to content
This repository was archived by the owner on Oct 14, 2020. It is now read-only.

Conversation

@J12934
Copy link
Member

@J12934 J12934 commented Jun 22, 2020

Closes #21

This includes some notable changes as the name of the jobs is no not deterministic anymore.

Before this PR change: a scan called: nmap-localhost
Would always create the same jobs:

  • scan-nmap-localhost
  • parse-nmap-localhost
    But the problem is this could result in to long job names (>= 63 chars).

After this PR these Jobs will always include a random element at the end and never be longer than 63 chars, like:
scan-nmap-localhost-8j7fm
parse-nmap-localhost-54z2m

J12934 added 5 commits June 22, 2020 12:39
Names are not totally reliable to find the jobs anymore when we truncate them.
This lets us add a `-` and 5 random chars to ensure unquire names.
Getting individual jobs is harder now, as the name has a random string at the end.
Listing all jobs is more helpfull anyway, as it also lists jobs for hooks
@J12934 J12934 added the bug Something isn't working label Jun 22, 2020
@J12934 J12934 requested a review from rfelber June 22, 2020 11:55
@J12934 J12934 merged commit ac9af9a into master Jun 23, 2020
@J12934 J12934 deleted the bug/object-name-truncation branch June 23, 2020 11:02
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issues with Max Length of kubernetes object

4 participants