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

Remove validation preventing both name and os for stemcells. #2485

Merged
merged 1 commit into from
Jan 9, 2024

Conversation

jpalermo
Copy link
Member

@jpalermo jpalermo commented Jan 9, 2024

Follow up to #2484, which broke everything...

Although those changes worked for full deploys, the way that manifests get parsed when doing things such as recreates causes the jobs to trip over the "cannot specify both name and os for stemcell" validation.

It would probably be possible to find some way to work around this, but the validation just isn't very useful anyway.

This commit removes that validation, making it valid now to specify both name and os.

When both are specified, name is given priority and os is ignored (as name has the os included in it anyway). It is now possible to make an invalid manifest, where the name and os don't actually match, but it will deploy anyway as long as the name is valid. This doesn't seem like a compelling reason to keep this validation around.

Copy link

linux-foundation-easycla bot commented Jan 9, 2024

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: jpalermo / name: Joseph Palermo (296ade2)

Although those changes worked for full deploys, the way that manifests
get parsed when doing things such as recreates causes the jobs to trip over the
"cannot specify both name and os for stemcell" validation.

It would probably be possible to find some way to work around this, but the
validation just isn't very useful anyway.

This commit removes that validation, making it valid now to specify both name and os.

When both are specified, name is given priority and os is ignored (as name has the os included
in it anyway). It is now possible to make an invalid manifest, where the name and os don't
actually match, but it will deploy anyway as long as the name is valid. This doesn't
seem like a compelling reason to keep this validation around.
@jpalermo jpalermo force-pushed the pr-remove-stemcell-name-and-os-validation branch from 6e9af42 to 296ade2 Compare January 9, 2024 06:49
@jpalermo jpalermo merged commit e74e435 into main Jan 9, 2024
4 checks passed
@jpalermo jpalermo deleted the pr-remove-stemcell-name-and-os-validation branch January 9, 2024 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

3 participants