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

Add support for resource classes in the Score spec #65

Closed
sujaya-sys opened this issue Oct 20, 2023 · 1 comment
Closed

Add support for resource classes in the Score spec #65

sujaya-sys opened this issue Oct 20, 2023 · 1 comment
Assignees
Labels
new feature/idea New feature or request

Comments

@sujaya-sys
Copy link
Contributor

sujaya-sys commented Oct 20, 2023

Detailed description

Sometimes it is neccesary to specialise a resource beyond just the type. For example, one workload might need an externally accessible s3 bucket and another might require one that is encrypted and only accessible to specific riles to store sensitive information.

Context

The class property allows developers to specialise the resource type. The concept is modelled on Kubernetes Storage Classes and works similarly. For example the workload that needs an externally accessible workload might set the class to external while the workload that requires an encrypted bucket might have a class of sensitive.

Example:

...
resource:
  external-bucket:
    type: s3
    class: external

Possible implementation

The score spec needs to be updated to include a class property in the resource object. The value of the class must be a valid ID, i.e. satisfy this regex: ^[a-z0-9]+(?:-[a-z0-9]+)*$

@github-actions
Copy link

We found the following entries in the FAQ which you may find helpful:

Feel free to close this issue if you found an answer in the FAQ. Otherwise, please give us a little time to review.

This is an automated reply, generated by FAQtory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature/idea New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants