What this PR does / why we need it:
Currently, checks are only in-place for retrieving Feast resources (Entities, FeatureTables, Features) and not in apply step, which is incorrect, as that may allow inappropriate project naming when applying new Feast resources.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:
Feast project names now allow alphanumerical, dashes and underscores.
Signed-off-by: Terence Lim terencelimxp@gmail.com
What this PR does / why we need it: Currently, checks are only in-place for retrieving Feast resources (Entities, FeatureTables, Features) and not in
apply
step, which is incorrect, as that may allow inappropriate project naming when applying new Feast resources.Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: