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

fix: remove deprecated 0-keys placeholder behavior #33

Merged
merged 1 commit into from
Apr 5, 2024
Merged

Conversation

astromechza
Copy link
Member

@astromechza astromechza commented Apr 4, 2024

There was some behavior inherited from an older version of score-compose that resolved 2 part placeholders like ${resources.<name>} to <name>. This was used as a mechanism to refer to certain resources in some contexts (like volumes). A similar mechanism exists in some parts of Humanitec's implementation.

This funcitonality was ported over to score-go, but can now be removed and any special behavior can be moved into the implementations respectively.

As an aside this PR also fixes some comments in other places that were incorrect.

This is what the score-compose PR would look like: score-spec/score-compose#103

Signed-off-by: Ben Meier <ben.meier@humanitec.com>
Copy link

@mathieu-benoit mathieu-benoit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@astromechza astromechza merged commit df173b3 into main Apr 5, 2024
2 checks passed
@astromechza astromechza deleted the bugfix branch April 5, 2024 12:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants