-
Notifications
You must be signed in to change notification settings - Fork 15
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
Change method of sanitising SRE names #2284
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Can this be a patch release, or will it break existing deployments? |
I guess it might break them, since the expected config names will now be different (although this should be fixable by reuploading the config). |
If you can write a workaround (download config, upgrade, upload config) then I think this can still be a point release. |
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just want to be careful we aren't reintroducing the same or a similar problem here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
I pushed a commit to swap the *
in regexes with +
so that blank strings are not allowed.
Not sure if it would cause errors but I don't think we expect to allow that.
We could also modify the annotated types to give them a minimum length.
✅ Checklist
Enable foobar integration
rather than515 foobar
).develop
.🚦 Depends on
Drops the
json_safe
function, which is only used to generate SRE filenames without non-alphanumeric characters. The SRE names from the config files are now used, with those names already being sanitised asSafeStrings
containing only alphanumeric characters, hyphens, and underscores, all of which can be included in filenames.This prevents issues with mismatches between the config filename and the SRE name in the config.
🌂 Related issues
Closes #2278
🔬 Tests
Tested locally